Forum Discussion
PBI Desktop Customising Slicer
- 1 year ago
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 ,
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]