Row limit in Hierarchy slicer's search function

[JayV]

In my .pbix i have this hierarchy slicer with the "search" tool, i see that it can only filter 30,000 rows

If i search a value higher than that it won't show on the slicer

Is there a way i can show all my data in this tool or is there a better way to do this? the distinct count of "Number Data" is 500,000
Thanks a lot!

[Anonymous · Accepted solution]

Hi @JayV ,

There are different types of slicers in Power BI, each with its own limitations. The Hierarchy slicer has a limit of 30,000 rows. You can experiment with different types of slicers, such as drop-down list slicers or list slicers. These slicers have no row limit and can display all data.
If you want to limit the number of options displayed in a slicer based on another slicer selection, you can use a custom visual object, such as OKVIZ's Smart Filter Pro. This visual object searches for multiple columns of data at once and has an unlimited row limit.

How to Get Your Question Answered Quickly - Microsoft Fabric Community

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[speedramps]

We want to help you but your description is too vaugue. Please write it again clearly.

Please DON'T copy & paste your DAX that does not work and expect us to fathom what you want to do. That is a bit crazy. 😀

Please just give a simple non technical functional decscription of what you want, then let us suggest the solution. Thank you.

Provide example input data as table text (not a screen print) so we can import the data to build a solution for you.
Provide example input data as table text (not a screen print) so we can import the data to build a solution for you.

Remove any unneeded columns which may cause confussion.

Rename columns to user friendly names.
Also provide the example desired output, with a clear description of the process flow.
Also provide the example desired output, with a clear description of the process flow.
Remember not to share private data ... we don't want you to get into trouble. 😧
Take time and care to use the same table and field names in the input, output and description so we can understand your problem and help you.
Try keep it simple and ask one question per ticket.
You will get a quick response if you put time, care and effort into writing clear problem descriptions.
Remember you are gerrting free expert help, so please put lots of proper effort to asking questions and providing example.

Vaugue descriptions can waste your time and ourtime.

Look foward to helping you when the above information is forthcoming

[JayV]

I'm sorry 😧, just finished editing the post so it is clearer, thanks you! 😃