Skip to main content
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

PBI RS Jan 2021: Microsoft Native Hierarchy Slicer with Search Option Issue

Hi There,

Currently we are using the January 2021 PBI RS native Microsoft slicer using the hierarchy functionality (adding multiple columns as layers). In the process have also turned on the "Search" capability. When using the search option, it narrows down the selection in any level of the hierarchy. Example: Searching for the word "Ford" would look at both the Vehicle and Brand column as pictured below. It then narrows down the selection to only showing items with "Ford".


Now, if there are many different versions of the word Ford the list starts to become large. You then think that when selecting the level above it > Cars, as a fast route instead of selecting each individual version of Ford, you would only get a count with what you searched for originally.


That is not the case. You are actually getting that level that you clicked on, count of Cars regardless of the brand (in this example 6 instead of desired 3). Ideally if you are using a search option and only seeing results for that lowest level, you would want a way to quickly select those options without having to individually click on them.
Actual Behavior:




Expected Behavior: (notice I had to select each individual lowest level option to get the count)




Status: New
Community Support

Hi @Anonymous ,

The 'Search' feature in the slicer is just to make the slicer look more clear and convenient to find the corresponding fields in it, it would not affect any other visuals in Power BI Desktop.


If you want to calculate the count as your mentioned, you can try to create a measure like this:

Count = 


Best Regards,
Community Support Team _ Yingjie Li

Not applicable

Power BI refresh error “could not load file or assembly…provided impersonation level is invalid”

Not applicable

Hi @v-yingjl ,

Unfortunately the DAX measure will not work for the use case. We would not like to hard code a value that will be searched, our users will want to search things dynamically so the ContainsString can't be used. Now, if there is a DAX measure that would only consider doing a distinct count at the lowest level of a hierarchy selected, that could possibly work - I'm not sure what this would look like or if it exists. Thoughts?

Thanks for your help.