Allow Parameters to be saved in Dataflows
At the moment, parameters cannot be created and saved in dataflows. Parameters are automatically converted to a table when saving the dataflow.
Parameters are useful to easily change or update specific values in SQL queries.
Yes they can (since November 2019) However ( unless i am wrong) they can't be used in a Query unless you have a Premium contract
We want to be able to allow the user to select the date range of data they want to have ingested through Data Flows otherwise the whole table gets pulled in, which can be a lot of records. Please ad a way to add a parameter to dataflows ASAP
The ability to "dynamicize" a Dataflow would be amazing. We do a lot of work connecting to multiple databases which share the exact same schema. Being able to define the dataflow as the source at run time would be amazing.
Andrew Simmans commented
It looks as though putting "Parameters" in makes the dataflows Computed and thus they need a Premium Account which is too expensive. One of the main benefits that I use parameters for is to switch the SQL datasource from Development to Live. To have to go into each dataflow and make this change is laborious.
Olivier Travers commented
Parameters can actually be saved in Dataflows, make sure to right click and uncheck Load in the online query editor. The UX will sure need to be improved though.
Please! I will be handing over a Power BI solution to end users who don't know much about Power BI. They are ok with editing parameters in Service or even in the front end of Desktop. Training people to edit parameters in Dataflows is a big draw back as it risks them making a mistake with code as well.