Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
I have a dataset with customers, contracts, delivery sites etc. Smal dataset and refresh takes appr. 2 minutes.
I have one dataflow with hour values. This one is quite large (300 million rows) but I'm using incremental refresh on this one (refresh last 2 of total 13 months). The refresh takes appr. 5 minutes. The data flow is set to refresh one hour before the dataset.
To include the dataflow in my dataset is where the trouble begins. In the dataset in Power BI Desktop I'm using Get data, Dataflow. Is this the way to do this? It starts to load the table into the dataset and it takes very long time.
The main issue however is the refresh of the dataset after indluding the data flow takes forever and often ends in "Not enough memory". One point of the dataflow is to avoid this, isn't it?
Looks like I've just increased the dataset (without incremental on the table with hour values). I'm a doing it all wrong?
The purpose of a dataflow is to shield you (the report developer) from a slow data source. Ingesting the dataflow into your dataset should be fast. If it isn't then maybe you are doing transforms after attaching to the dataflow.
You can do incremental refresh on your dataset if you want. Also note that with enhanced and XMLA based dataset refresh you have more flexibility on when to refresh which partition.
Also note that you can use Power Automate to chain the refreshes - initiate dataset refresn when the dataflow refresh has completed etc.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 44 | |
| 44 | |
| 37 | |
| 25 | |
| 25 |