Forum Discussion
Export Failure in Power BI Using Power Automate with Slicer-Based Campaign Selection
- 6 months ago
Hello JibinSebastian,
The export is failing because the underlying dataset query is exceeding the Power BI query memory limit.
The error rsQueryMemoryLimitExceeded (2048 MB limit) indicates that when the Power Automate button triggers the export, Power BI executes a DAX query for the entire visual result set. Since your table visual pulls columns from multiple tables and you are attempting to dynamically include the selected Campaign from the slicer, the query becomes more complex and exceeds the per-query memory limit.
The error is generated by the Power BI engine, which enforces resource governance limits on dataset queries.Recommended Approach
Instead of adding the selected Campaign as a column in the visual:
Keep the slicer filtering the report normally.
Pass the selected Campaign value to Power Automate as a parameter.
In the flow, use Run a query against a dataset (or filter during export) using that parameter.
This avoids expanding the visual query and prevents the memory limit error.
If you must include it in the visual, use a simple measure:
Selected Campaign = SELECTEDVALUE('Campaign'[Campaign Name])
Also ensure:
Proper one-to-many relationships
No unnecessary high-cardinality columns
Avoid many-to-many or bi-directional filtering unless required
In summary, the failure is caused by the dataset query exceeding Power BI’s memory limits during export.
Hello JibinSebastian,
The export is failing because the underlying dataset query is exceeding the Power BI query memory limit.
The error rsQueryMemoryLimitExceeded (2048 MB limit) indicates that when the Power Automate button triggers the export, Power BI executes a DAX query for the entire visual result set. Since your table visual pulls columns from multiple tables and you are attempting to dynamically include the selected Campaign from the slicer, the query becomes more complex and exceeds the per-query memory limit.
The error is generated by the Power BI engine, which enforces resource governance limits on dataset queries.
Recommended Approach
Instead of adding the selected Campaign as a column in the visual:
Keep the slicer filtering the report normally.
Pass the selected Campaign value to Power Automate as a parameter.
In the flow, use Run a query against a dataset (or filter during export) using that parameter.
This avoids expanding the visual query and prevents the memory limit error.
If you must include it in the visual, use a simple measure:
Selected Campaign = SELECTEDVALUE('Campaign'[Campaign Name])
Also ensure:
Proper one-to-many relationships
No unnecessary high-cardinality columns
Avoid many-to-many or bi-directional filtering unless required
In summary, the failure is caused by the dataset query exceeding Power BI’s memory limits during export.
Thank you Olufemi7 for helping me to resolve the issue. Appreciate your efforts and time