Forum Discussion
PBI Desktop Customising Slicer
Hi I have a requirement to customising the slicers in my dashboard. In drop down option, by default "select all" option would be there but I have to rename it into customised texts. For eg instead of "select all" it must show as "All Use Cases". I have got a solution that I can create a disconnected table with the specific column then later on create a measure to connect it so that only filtering will work. But the problem is I have more than 10 slicers like that in a single page so would it be the best practice to do so? It would be like cluttered but I can hide it still I am thinking would that be the best way to do this? Any other options please? Thanks in advance
Hi kichu123 ,
Unfortunately, Power BI does not support renaming the built-in “Select all” option in slicers — it's hardcoded by the platform and cannot be directly customized through formatting or DAX.
So your workaround using disconnected tables and DAX-driven measures to simulate slicers is a common and valid approach. But with 10+ slicers on one page, performance and manageability become real concerns.
If we workaround your approach
- Keep Using Disconnected Tables (with Best Practices)
It’s a viable method. But to optimize and scale it:- Re-use generic disconnected slicer tables if possible (e.g., a shared “Yes/No/All” table).
- Use field parameters if they help you centralize logic.
- Store hidden slicer tables in a separate hidden page to reduce visual clutter.
- Use a patterned naming convention for easier management in the Model view.
- Consider using DAX switch-based filters for visuals using your slicer selections.
Pros: Full control over slicer labels and behavior
Cons: Extra maintenance, potential confusion for future developers
- Use a Button + Bookmark Combo
If user experience is critical and you want precise labels like "All Use Cases", you can replace slicers with:Toggle buttons (or dropdown-style buttons) + Bookmarks to simulate slicer behavior.
Combine with selection pane and visibility controls.
Pros: Highly customizable UI/UX
Cons: Doesn’t scale well, harder to maintain logic (especially with 10+ slicers)
Live with “Select All” (but Reframe UX)
If none of the above is scalable enough, consider keeping the default "Select all" but improving the context:Add a custom label or tooltip near the slicer to explain that “Select all = All Use Cases”.
Use visual cues (info icon, help tooltip, text box).
Sometimes minor UI compromises avoid major complexity.
⭐Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
🚀Let’s keep building smarter, data-driven solutions together! 🚀 [Explore More]- Keep Using Disconnected Tables (with Best Practices)
2 Replies
Hi kichu123 ,
Unfortunately, Power BI does not support renaming the built-in “Select all” option in slicers — it's hardcoded by the platform and cannot be directly customized through formatting or DAX.
So your workaround using disconnected tables and DAX-driven measures to simulate slicers is a common and valid approach. But with 10+ slicers on one page, performance and manageability become real concerns.
If we workaround your approach
- Keep Using Disconnected Tables (with Best Practices)
It’s a viable method. But to optimize and scale it:- Re-use generic disconnected slicer tables if possible (e.g., a shared “Yes/No/All” table).
- Use field parameters if they help you centralize logic.
- Store hidden slicer tables in a separate hidden page to reduce visual clutter.
- Use a patterned naming convention for easier management in the Model view.
- Consider using DAX switch-based filters for visuals using your slicer selections.
Pros: Full control over slicer labels and behavior
Cons: Extra maintenance, potential confusion for future developers
- Use a Button + Bookmark Combo
If user experience is critical and you want precise labels like "All Use Cases", you can replace slicers with:Toggle buttons (or dropdown-style buttons) + Bookmarks to simulate slicer behavior.
Combine with selection pane and visibility controls.
Pros: Highly customizable UI/UX
Cons: Doesn’t scale well, harder to maintain logic (especially with 10+ slicers)
Live with “Select All” (but Reframe UX)
If none of the above is scalable enough, consider keeping the default "Select all" but improving the context:Add a custom label or tooltip near the slicer to explain that “Select all = All Use Cases”.
Use visual cues (info icon, help tooltip, text box).
Sometimes minor UI compromises avoid major complexity.
⭐Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
🚀Let’s keep building smarter, data-driven solutions together! 🚀 [Explore More]- Keep Using Disconnected Tables (with Best Practices)
Hi kichu123 ,
You're right, that "Select all" text is hardcoded and it's annoying when you need custom labels.
Honestly, with 10+ slicers, disconnected tables will become a nightmare to maintain. You'll end up with a cluttered model and tons of measures to manage.
Better options:
Try custom visuals first - Check out Chiclet Slicer or Smart Filter Pro from AppSource. Some of these actually let you customize the "Select all" text without all the DAX gymnastics.
If you must go the disconnected route:
- Create one generic "All/Specific" table and reuse it where possible
- Hide all the helper tables on a separate page in your model
- Use consistent naming like "Slicer_UseCases", "Slicer_Regions"
Real talk: Unless your users are genuinely confused by "Select all", you might be overengineering this. Clear slicer titles like "Use Cases" instead of "FieldName_ID" often solve the user experience issue without the technical debt.
What's the actual user feedback you're getting? Are they struggling with the interface, or is this more of a "nice to have" requirement?
Sometimes the best solution is the one that doesn't break when someone else has to maintain your report in 6 months.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.
