Forum Discussion
DataflowsError
Hi ArvindJha - These errors are common when there is a data packet being processed in your Power BI Dataflow exceeds the maximum allowed size
Try limiting the number of rows or columns processed in your Dataflow:
Try reducing columns, filtering data, and enabling Incremental Refresh first. If the issue persists, check gateway memory and consider partitioning your data.
option 2: If possible, split large tables into smaller tables and process them separately
ref: link:
Troubleshooting Dataflows in Power BI | Power Query Tutorial Ep8 | Power BI | BI Consulting Pro | 4K
- ArvindJha1 year agoHelper III
Thanks for the response all of this is already taken care of still the issue persists , for incremental load to happen it has to do full load first time right ? colums are reduced to what is required , it works absoultely fine in QlikSense
- Anonymous1 year agoNot applicable
Hi ArvindJha,
Thanks for reaching out to the Microsoft fabric community forum.
You're right about Power BI requiring a full load initially when Incremental Refresh is enabled, and it sounds like you've already optimized the dataset thoughtfully.
One thing to consider is how the query steps are structured within the dataflow. If a particular transformation (like a merge, append, or expand) results in a very large in-memory object even briefly it can cause a single packet to exceed the allowed uncompressed size, leading to this error. Unlike QlikSense, Power BI doesn’t stream all data step-by-step during transformation and might materialize intermediate results in memory depending on how the query is built.
If possible, try reviewing the query steps to see if a specific operation may be generating a large intermediate dataset. Breaking that transformation into smaller steps, perhaps by materializing earlier steps into a staging Dataflow or applying filters earlier in the chain can help distribute the load more evenly.
I would also take a moment to thank rajendraongole1, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
- ArvindJha1 year agoHelper III
There is no transformation , it is extraction dataflow only i am reducing the columns from 150 to 20 , qliksense is even working with 50 columns , pbi fails with 20 columns , in some cases actually the problem is a column called REASON which is text field ranges from 0-255 characters , if i reduce column size to 20 it works in some cases , in other cases even that does not work where the qvd size in qlik exceeds 5 GB , Power BI is unable to handle , so does it mean that PBI cannot handle such huge data?