ReportLevelFilters is not working using PowerAutomate

[mokumar]

Hi All,

I am trying to email a report with the help of PowerAutomate using the action Export To Files for Power BI Reports (more info can be found here )

that is how the action looks like with a filter (TableName/ColumnName)- 

In history - 

The reports I am getting are empty, without any data. What is missing here?

[mukuljuyal]

I had tried even with one filter but that is also not working with same result, i am using sql as backend

[LaurenNick]

Make sure that when you published the report, there were't any filters applied (ie clear the filter).  Otherwise the default filter applies aswell as what you are applying in the power automate flow and you will get no result.

[mokumar]

@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_subm... eq 'f57e5f3f-25c8-4a6e-9c35-66940895564a'

https://app.powerbi.com/groups/grouo_guid/reports/report_guid?filter=cr60a_CostTreeDetail/cr60a_subm... 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.

[AmosHersch]

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

[bchager6]

@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]

@bchager6 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'"

[bchager6]

@AmosHersch  Thanks for your response. I would love to see a working example of what you described. I've tried the approach noted in the link you shared as well as various other iterations of the filter parameter, and nothing's worked for me.

[AmosHersch]

Hi @mokumar ,

When such issues happen it's most of the time has to do with the filter string itself.

The best way to sort out what's wrong in open the same report in Power BI portal, append the same filter string to the browser URL as explained here: https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-url-filters

Once you get it to work as expected, the exact same string (without the "?filter=" part, and no need for the URL encoding, only special characters if exists) should work when you export through Power Automate.

[mukuljuyal]

my url filter Clusterdaily/RecordDate%20gt%202023-12-23T00:00:00Z%20and%20Clusterdaily/Cluster%20eq%20'01-C'

is working fine but not working when i am using it in export through power automate 

Clusterdaily/RecordDate gt 2023-12-23T00:00:00Z and Clusterdaily/Cluster eq '01-C'

[LaurenNick]

I donyt think you can use multiple filters when exporting PBI via PowerAutomate