Export Failure in Power BI Using Power Automate with Slicer-Based Campaign Selection

[JibinSebastian]

I have a table visual that includes columns sourced from multiple tables. There is also a slicer with three campaign names and a Power Automate button used for exporting the data.

I would like the exported file to include a column that reflects the selected campaign name from the slicer at the time of export. However, when I attempt to include this and trigger the export using the Power Automate button, the flow fails.

Could you please help identify why the export is failing and advise on the correct approach to include the selected campaign name in the exported output?

[V-yubandi-msft]

Hi @JibinSebastian ,

@lbendlin & @Jai-Rathinavel, has correctly pointed out the issue and shared a few steps to follow. Have you tried those steps, and did they help? If you are still facing any issues or need additional information, please let us

Thanks for your valuable response @Olufemi7 , @lbendlin  .

Regards,

Yugandhar.

[Olufemi7 · Accepted solution]

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:

1. Keep the slicer filtering the report normally.

2. Pass the selected Campaign value to Power Automate as a parameter.

3. 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.

[JibinSebastian]

Thank you @Olufemi7 for helping me to resolve the issue. Appreciate your efforts and time

[lbendlin]

The best way to make sure the table visual and the Power Automate visual have identical behavior is to make them identical. Copy the table visual and change the visual type of the copy to Power Automate. Then, if you need to transport slicer selections over to Power Automate, add that column to the visual too.

Your issue lies elsewhere - likely you included columns in the Power Automate visual that come from unrelated tables and that then cause a cartesian product, resulting in memory starvation.  Re-check your data model.

[Jai-Rathinavel]

@JibinSebastian Try making the campaign name as a measure using below DAX and it to the table visual then try exporting it.

Campaign Name = SELECTEDVALUE(Table[Camp_Name])

Thanks,

Jai