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?

[alen_rl]

@AmosHersch 

My power automate job worked perfectly for 2 years until last month. Few of the filter values are not working since last month but the rest is working fine. I am not sure what happened as the data looks good and the url remains the same when filtered as query string in our powerbi workspace. 

[AmosHersch]

@alen_rl what happens if you open your report in Power BI web portal and try the same filter in the URL as described here Filter a report using query string parameters in the URL - Power BI | Microsoft Learn?
Does it filter correctly?

[alexkarwoski]

alexkarwoski

New Member

In response to LaurenNick

2 seconds ago

I have a similar problem.

Currently I have three filters, two only allow for 1 selection and the other allows for multiple. Lets call them state, name and age respectively.

Essentially what I want to do is iterate through these filters in power automate and generate a report for each state, name, age combination. For example, say state was GA, name was Alex, and age was 1,2, and 3. I want to click a Power Automate button in Power BI. I want generate the report for a certain page using Export for Power BI Report in power automate for the combinations
GA,Alex, 1
GA,Alex, 2
GA,Alex, 3

I have this all set up. And when I check the filters that were passed this is exactly what they are. However, the report is the same for all three pages. It shows the merged summary from having the multiple selections. I am on a premium capacity server, and have been stuck for a few days.

Any thoughts?

[arnemenzo]

I can't make this filter function work in Power Automate. It works well using Service URL String but when applied to Power Automate Export to File for Power BI Reports - Report Level Filters, it never worked! Spent 3 days already still no resolution.

I have applied any possible filters in the ReportLevelFilters parameters, still the generated ouput is the default view/visual room. 

[Anonymous]

@arnemenzo Bookmarking the filter state and using that instead works for me.

[arnemenzo]

Thank you @Anonymous! Yes, indeed this is a best solution if the we're dealing with few sets of value filters. But with my case, I'm dealing for over 100 different sets of value filter. Plus, the values are dynamic (like the next day, new category is added). Report Level Filter must be the best option in this case. The thing is, I can't make it work

Can you spot where the problem is?

Table Name: Main - Rejected VIM Invoices
Column Name: Market Area
Exporting PNG Image: Already enabled at Tenant Level
My PBI Workspace Access: Contributor Role

This is just a sample but the actual case would use a dynamic filter (i.e. Country Name/Category Name) which expects to generate around 100 different snapshot images per country. For illustration purposes, I'm using Market Area.

[LaurenNick]

Can you post a snip of what you care currently doing?

[arnemenzo]

@LaurenNick 

Can you spot where the problem is?
Table Name: Main - Rejected VIM Invoices
Column Name: Market Area
Exporting PNG Image: Already enabled at Tenant Level
My PBI Workspace Access: Contributor Role

This is just a sample but the actual case would use a dynamic filter (i.e. Country Name) which expects to generate around 100 different snapshot images per country. For illustration purposes, I'm using Market Area.

[alexkarwoski]

alexkarwoski

New Member

In response to LaurenNick

2 seconds ago

I have a similar problem.

Currently I have three filters, two only allow for 1 selection and the other allows for multiple. Lets call them state, name and age respectively.

Essentially what I want to do is iterate through these filters in power automate and generate a report for each state, name, age combination. For example, say state was GA, name was Alex, and age was 1,2, and 3. I want to click a Power Automate button in Power BI. I want generate the report for a certain page using Export for Power BI Report in power automate for the combinations
GA,Alex, 1
GA,Alex, 2
GA,Alex, 3

I have this all set up. And when I check the filters that were passed this is exactly what they are. However, the report is the same for all three pages. It shows the merged summary from having the multiple selections. I am on a premium capacity server, and have been stuck for a few days.

Any thoughts?

[LaurenNick]

Report Level Filter Sample 3 looks close but try adding a _x0020_ between Market and Area.

I think I ended up creating duplicate columns in my data that didn't have the spaces as this was driving my bonkers

[arnemenzo]

@LaurenNickwe've finally figured out where the problem is. Power BI Rest API is not enabled for Power Automate at the Tenant Level. So we have to go through the App Registration in my case.

This article helped my issue: Call Power BI Rest APIs with Power Automate (vahiddm.com)

[alexkarwoski]

Good Afternoon!

So I am struggling with this issue currently. Can you eleborate what you mean by using the App Registration? Is this where the report will sit? And then will it work as intented? Or did you change the Flow to use the rest API instead.

Thanks

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

[Anonymous]

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

[Anonymous]

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