Proposal: Selector Mode for Slicers, or a New 'Selector' Visual Slicers, by their name, imply a specific function: slicing data. But from a UX perspective, what users actually want to do is select values of interest—which just so happens to result in sliced data. The current behavior of slicers creates confusion: When nothing is selected, the slicer shows everything (because no slicing occurs). But users interpret "nothing selected" as "I haven’t made a choice yet," which should logically mean "show nothing." Worse, enabling "Select All" adds a second way for everything to be selected—now we have two distinct UI states that both result in the same outcome. One makes sense; the other does not. This mismatch between user expectation and slicer logic leads to awkward DAX workarounds, countless forum posts, and tutorials explaining how to fix something that should just work. Proposal: Either add a "Selector Mode" toggle to slicers, where 0 selections = 0 records shown, Or introduce a new 'Selector' visual that behaves like a slicer in every way except how it handles the empty state. This would improve UX clarity, reduce user confusion, and eliminate the need for workaround logic in a common scenario. If we as developers can handle this with DAX, then surely the platform itself can handle it natively so everyone benefits.
... View more
dm-p
on:
Allow standard Focus Mode for custom visuals that ...
on:
Data Pipelines - Run only selected activities
on:
More granular control and better design experience...