Forum Discussion
Dataflow +Dataset = NEED more Clarity!
Here is another shining example of how the way Dataflow fetches data on Desktop forever and ever. Not an ideal way to start development of a report. Why cant it just give us a preview or sample of few 1000s?
MAKE ABSOLUTELY NO SENSE to download every data to the desktop!
- jeffshieldsdev6 years ago
Solution Sage
I would start in Power BI Service, create a derived Dataflow that filters to the data you need and then connect to that new Dataflow from Power BI Desktop.
You could also create a "Sample" Dataflow, with a few hundred records to enable report creation and then switch to the full Dataflow before publishing the report to service.
- Anonymous6 years agoNot applicable
Thanks. But the problem is every-time you switch it starts downloading the data again right?
- jeffshieldsdev6 years ago
Solution Sage
Correct, Anonymous you'll eventually need to download all the data to Desktop to publish--but at least this eases report creation.
I'm pretty sure DirectQuery is coming to Enhanced Dataflows Compute Engine, so maybe there will be options to limit data during report creation too :)
EDIT: Actually, no--you don't have to download everything to Desktop if you don't remove the filter from the derived Dataflow until after publish. From MatthewRoche 's blog
"Quick Tip: Developing with large dataflows
- Develop and test the dataflows in the Power BI service
- Add filters to the too-large dataflow entities’ queries[2] to reduce the number of records in the entities
- Refresh the dataflow
- Develop the model and reports in Power BI Desktop
- Publish the model and reports to the Power BI service
- Remove the filters from the filtered dataflow entities
- Refresh the dataflow
- Refresh the dataset"