Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

Slicer "None Selected" versus "All Selected" Behavior

It would be helpful if the slicer could pass-through NO data when nothing is selected so that downstream visuals don't return errors or consume resources trying to ingest all the data.

Currently the slicer treats the "all selected" and the "none selected" states as identical, returning the full data. This is needed and desirable in many situations.

The slicer could have an option where the behavior of the "none selected" state could be set to "same as all selected" or could be set to "no data selected". This would allow the report designer to match the behavior to the need. For example, if the full data breaks the limits of a downstream graph, leaving the slicer unselected would leave the graph empty instead of displaying an error. Then, once at least one selection is made in the slicer, the selected data would be passed as normal.

There are some situations where this can be accomplished with measures, but they are clunky and not always possible.

Status: New