odata Report Level Filters Multiple Filters Same Column

[BrianNeedsHelp]

I have this in the Report Level Filters of Power Automate on the 'Export To File for Power BI Reports' operation.  The filter doesn't work when applying multiple criteria to the same column.  

Current_x0020_Hierarchy/Level3Value eq 'Bob Smith' or Current_x0020_Hierarchy/Level3Value eq 'James Brown'

I tried this also:  

Current_x0020_Hierarchy/Level3Value in ('Bob Smith','James Brown')

The filter works if I only have one value.  Any other way to make this work?  

[rohit1991]

Hi @BrianNeedsHelp 

Could you please try the following :

• The Export to File request accepts only one report level filters entry; you must put your entire filter in that single string.
• Inside that string, use the in operator to match multiple values of the same column (Power BI URL-filter syntax). or isn’t in the supported operator list. Example:
  

  Current_x0020_Hierarchy/Level3Value in ('Bob Smith','James Brown')​

Table/column names are case-sensitive and spaces/special chars must use the _x0020_ style; use straight quotes and escape apostrophes with ''.
Reference:
https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-url-filters

[Poojara_D12]

Hi @BrianNeedsHelp 

You're trying to apply a report-level filter in the "Export To File for Power BI Reports" action within Power Automate, and you're facing an issue where filtering on multiple values in the same column doesn't work as expected. When using a single value—for example, Current_x0020_Hierarchy/Level3Value eq 'Bob Smith'—the filter works correctly. However, when you try to filter using multiple values using either the or operator or the in syntax like ('Bob Smith','James Brown'), it fails to apply.

This issue arises because the Power BI REST API, which underpins this Power Automate action, expects OData-style filter syntax, but it doesn't support complex logical expressions (like multiple OR conditions or in clauses) reliably in report-level filters, especially when referencing fields with encoded names (e.g., spaces as _x0020_) or within nested structures like Current_x0020_Hierarchy/Level3Value.

As a workaround, the safest and most reliable method is to create a DAX measure or a report-level parameter inside the Power BI report that filters based on a slicer or a field that can accept multiple values. Then, you can pass that filter using Power Automate by binding to that slicer field, or use the bookmark + slicer approach if exporting a specific view.

Alternatively, if your use case demands automation, you can export multiple files—one per value—by looping through a list of filter values ('Bob Smith', 'James Brown', etc.) and applying them one by one via the Power Automate action. While this isn't as elegant as passing multiple values at once, it aligns with what the API currently supports.

In summary, Power BI's export API doesn't fully support multi-value filtering in a single report-level filter expression. To work around it, consider using individual exports in a loop or redesign the report to filter internally via parameters or slicers that are more automation-friendly.

[BrianNeedsHelp · Accepted solution]

Thanks for the detailed explanation.  As I had mentioned in my previous post, I solved this by using bookmarks in PBI and referencing those in the "Export To File for Power BI Reports" action.  

[v-menakakota]

Hi @BrianNeedsHelp ,

As you mentioned in the previous post that you have solved the issue by using the bookmarks in PBI can you please mark  your solution as Accept as Solution ,so that others can find it easily.

Thank you.

[v-menakakota]

Hi @BrianNeedsHelp ,

We really appreciate your efforts and for letting us know the update on the issue.

Please continue using fabric community forum for your further assistance. 

If this is the solution that has worked for you please accept your reply as solution so as to help other community members who may face similar issue in the future.

Thank you.

[v-menakakota]

Hi @BrianNeedsHelp ,

We really appreciate your efforts and for letting us know the update on the issue.

Please continue using fabric community forum for your further assistance. 

If this is the solution that has worked for you please accept your reply as solution so as to help other community members who may face similar issue in the future.

Thank you.

[SacheeTh]

Ithin this 'in' doesn’t work preperly:

OData does not support in in the way SQL does. While newer APIs like Microsoft Graph support in, Power BI's Export API does not support it reliably.

try following fo the best pactices that we are using on day today work.

If this continues to fail:

• Modify the report to include a multi-value parameter (like a slicer with "Bob Smith" and "James Brown").

• Use a bookmark or hidden page filtered only to these values.

• Or, split the automation to export each user separately.

[SacheeTh]

try this method putting 'or'

Current_x0020_Hierarchy/Level3Value eq 'Bob Smith' or Current_x0020_Hierarchy/Level3Value eq 'James Brown'

 bash

Current_x0020_Hierarchy/Level3Value eq 'Bob Smith'%20or%20Current_x0020_Hierarchy/Level3Value eq 'James Brown'

[lbendlin]

the "in"  version should work 

OData IN Operator filter function - OData | Microsoft Learn

Check the spelling of your filter values, not sure if it is case sensitive.

[BrianNeedsHelp]

I checked it very thoroughly, and it still wouldn't work.  I ended up using the bookmark option with page name, and it works pretty well.