Forum Discussion
Passing parameter to dataflow from Power BI desktop
Thanks lbendlin for the response.
As per my understanding the primary use of dataflows are to maintain a single point of truth and reusability of data transformations - by separating the ETL layer from the data models (datasets). And that is the exact business requirement that we have!
Apart from that as I said, we need to be able to manage large volume of data with a pro license (data needs to be imported as direct query not suitable for our use cases). All data we are importing would change & there is no static part - so don't think incremental refresh would be of much use.
Thanks,
Rishi
"the primary use of dataflows are to maintain a single point of truth and reusability of data transformations"
Meh. That's what your corporate data stewardship system/data warehouse is for (Azure Purview/CDS/Dataverse and its competitors). Dataflows are not adequate for that - for example they have no guaranteed survivability. You will have scenarios where your dataflow borks down and you have to start over. Not something you want to experience with your data warehouse.
"All data we are importing would change & there is no static part"
Yes, that's a tough one. You need differential refresh and/or the equivalent of CDC. The more people need this the more pressure we can exert on Microsoft to finally support it.