Organization Name
Vlamis Software Solutions
Description
It would be great to be able to selectively promote My Calculations from a Data Visualization project to a Data Set. Many times it's easiest to work directly in the project canvas and create new calculations. Some features don't work with custom calculations, so you need them to be in the proper data set. Some custom calculations you may want to promote to the data set, some you may not. For example, you may want different color assignments for different visualizations/canvases. This is project specific and there's no real need to have duplicate columns in the data set. Other calculations evolve as you write them and then you do want to promote them to the data set definition so that it's much easier to share the calculations between projects without having to replicate the project. (I know, I know, delete the canvases and save the project with a new name using "save as" and you can start with your custom calculations in a new project, but they're still not part of the data set.)
Use Case and Business Need
This feature would also help reinforce the idea of pushing calculations down the stack. That is, from project to data set to subject area to data warehouse to ETL. Each step there's more process associated with a particular calculation. There's a natural trade off between the time it typically takes to add a data element and the availability, appropriate standards being applied, validation, security/access rules, conformed dimensions, and perhaps most importantly, system compute performance. Theoretically, every data element has its own "sweet spot". You don't want to burden developers and add to system overhead with seldom used calculations, but you also want calculations to be as consistent and performant as possible.
More details
Takes time to recreate calculations in the data set editor or in a data flow or in BI Admin tool.
Original Idea Number: 5fa771315d
