hierarchical slicers as intersections (vs unions)

[patBear]

For hierarchical slicers, is there an option to have multiple selections operate as "intersections" rather than "unions"?  Here's an example to better explain.  For the slicer below, if I select "Mountain Bottle Cage" and "Road-150 Red, 44," the visuals will show me the union of this data.  What if I want to see the intersection: Road-150 Red bikes that come with a Mountain Bottle Cage?  (I'm limited on space so I'm not wanting multiple slicers if possible.)  Thanks.

[Shaurya · Accepted solution]

Hi @patBear,

The first solution that comes to my mind to is to use two different slicers but since you've clearly mentioned that you don't want to take that approach, I suggest to go for some DAX that changes the OR logic in slicers to AND.

Here's a link that I have which will guide you how to do that.

https://medium.com/seismic-data-science/changing-or-to-and-logic-for-power-bi-slicers-1a6b20aee5f5

Works for you? Mark this post as a solution if it does!
Consider taking a look at my blog: Forecast Period - Previous Forecasts

[patBear]

Thanks @Shaurya, this is exactly the article I needed!!