Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
monty
Advocate I
Advocate I

Use of OData IN operator instead of ORs

Currently, when multiple values are selected for a column (as shown here for a table of financial transactions partitioned on the column "Division"):

 

monty_0-1626674834922.png

 

the generated OData contains a list of OR-ed elements, like:

 

 

$filter=Division eq 868041 or Division eq 868045 or Division eq 868046 or Division eq 868047

 

 

 

Is there any way to convince Power BI to use the new IN operator?

 

The IN operator is for database servers such as Invantive SQL in general easier to optimize than OR.

 

Some background is on https://forums.invantive.com/t/optimize-odata-filters-to-improve-performance/1379

1 ACCEPTED SOLUTION
mahoneypat
Employee
Employee

Did you try this syntax?

 

$filter=Name in ('Milk', 'Cheese', 'Donut')

 

Pat

 





Did I answer your question? Mark my post as a solution! Kudos are also appreciated!

To learn more about Power BI, follow me on Twitter or subscribe on YouTube.


@mahoneypa HoosierBI on YouTube


View solution in original post

4 REPLIES 4
mahoneypat
Employee
Employee

How do your users select values?  From your pic, it seems like they are editing the query directly to get different results.  Why not load all the data and create a slicer in your report?

 

If you do need the users to modify the query, you could have them provide a comma delimited list as a string parameter that you parse into a list with Text.Split for use in the database call.  Or you could have another query for the selection, and then make a list from that to use in the main query that make the database call.

 

Pat

 





Did I answer your question? Mark my post as a solution! Kudos are also appreciated!

To learn more about Power BI, follow me on Twitter or subscribe on YouTube.


@mahoneypa HoosierBI on YouTube


The awkward thing is that we are an ISV of an OData proxy for 70+ cloud platforms (Invantive Cloud). The software is used for 20.000 companies, but we typically do not directly assist users that build reports and these are typically finance professionals with little time to learn DAX. Therefore I was looking whether we can provide a really simple and actionable tip or guidance how Power BI out-of-the-box can be convinced to use the IN-operator.

It is good to know that this is currently not possible. I will ask our SQL engine team to work on an optimization to rewrite the OR-ed terms into an IN. That should do the trick too. Thanks!

mahoneypat
Employee
Employee

Did you try this syntax?

 

$filter=Name in ('Milk', 'Cheese', 'Donut')

 

Pat

 





Did I answer your question? Mark my post as a solution! Kudos are also appreciated!

To learn more about Power BI, follow me on Twitter or subscribe on YouTube.


@mahoneypa HoosierBI on YouTube


Hi Pat, thanks for the tip. Yes, the OData syntax is supported and works. However, I seem unable to convince Power BI Desktop to generate an IN instead of an OR when an end user just picks some values from the user interface. Educating them is quite costly.

Regards,

Guido

Helpful resources

Announcements
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.

Top Solution Authors
Top Kudoed Authors