Forum Discussion
ReportLevelFilters is not working using PowerAutomate
AmosHersch - I have tried this earlier. In my case when I use Page Level filters then my report looks like this -
when I use filters in the query string, it's completely different. I can see data in the blank fields as well. Here is the query string(data source is CDS)-
https://app.powerbi.com/groups/grouo_guid/reports/report_guid?filter=cr60a_CostTreeDetail/cr60a_submissionid eq 'f57e5f3f-25c8-4a6e-9c35-66940895564a'
https://app.powerbi.com/groups/grouo_guid/reports/report_guid?filter=cr60a_CostTreeDetail/cr60a_submissionid eq 'f57e5f3f-25c8-4a6e-9c35-66940895564a'
https://app.powerbi.com/groups/grouo_guid/reports/report_guid/ReportSection9a330f02804c7ab90fd0?filter=CostTreeDetail/cr60a_submissionid eq 'f57e5f3f-25c8-4a6e-9c35-66940895564a'
In the filter string I have tried both options- The internal name of the table and column and the display name.
AmosHerschMicrosoft Employee
mokumar I can't tell why it's not working for you in the API, but as I said whatever works in the URL query string (same table name/column name, filter value) is expected to work in the export API, and the report page should look the same as in the portal.
AmosHersch Can you provide an example of how that would look in Power Automate? Do the table name, column name, and filter value all need to be in the ReportLevelFilters section?
- AmosHersch
Anonymous same thing that works for you in Power BI portal URL, for example:
As described here Filter a report using query string parameters in the URL - Power BI | Microsoft Learn for filtering on a field you append to the URL:
?filter=Store/Territory eq 'NC'
So in the API it's equivalent to setting:
ReportLevelFilters = "Store/Territory eq 'NC'"