Power BI slicer selection not dynamically updating the Power Automate flow-generated certificate.

[akshayshiyani]

My Power Automate flow is correctly triggering a Power BI report export process, but the issue seems to be that the slicer selections are not dynamically reflecting in the exported report.

[akshayshiyani]

I have three different filters: one for company name, one for the time period (which ranges from 01/01/2021 to 01/01/2025), and one for customer number. Based on my requirements, these filters can be adjusted, which in turn changes the KPIs. I want to dynamically add these KPIs to a Word template, and at the end, generate a certificate. The previous suggestions were not working.

[Anonymous]

Hi @akshayshiyani,

In fact, current only the filter effect which actually saved to the report will be enabled when you export report.

If you mean operations on the report 'read view' mode, these changes did not applied when you export.

Regards,

Xiaoxin Sheng

[Anonymous]

Hi @akshayshiyani ,

Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.

If these also don't help, please share more detailed information and description to help us clarify your scenario to test.

How to Get Your Question Answered Quickly 

Regards,

Xiaoxin Sheng

[Poojara_D12]

Hi @akshayshiyani 

Your issue likely stems from how Power Automate handles slicer values when exporting a Power BI report. When exporting via Power Automate, slicer selections need to be explicitly passed as filter parameters in the "Export to File for Power BI Reports" action. If the slicer selections are not included, the report will export with the default state rather than the dynamically selected values.

To ensure slicer selections are applied:

• Use the "Apply Report Filters" option in the Power Automate action.
• Construct a filter string in OData format (e.g., table/column eq 'value').
• If using a Power Apps-triggered flow, ensure the selections are passed as dynamic values into the filter parameter.
• If your slicers are based on relative time (e.g., "Last 30 days"), ensure they are configured as report-level filters rather than slicers to persist across sessions.