Back to Native libraryWorking example Designer ↔ BI developer handoff More in Filtering
Slicers
Native visualDropdown, list, multi-select and search slicers with a reset state.
Department
1 selected
Employees7 rows
- Operations236 h
- Retail254 h
- Finance146 h
- IT245 h
What it is
A slicer is a visual that filters other visuals on the page (or across pages when synced).
When to use it
Users must narrow the dataset themselves and see the active selection at all times.
Native Power BI capability
Yes — List, Dropdown, Tile, Between/Relative date slicers, search box, Select all, sync slicers.
UX considerations
- Specify default selection, single vs multi-select and whether search is needed.
- Group slicers in one predictable region of the page.
- Always provide a visible reset path (Clear all slicers button or bookmark).
BI developer considerations
- Enable the search box in the slicer header menu for long lists.
- Use Sync slicers to keep filter context across pages.
- Consider Apply buttons on slow models so one refresh runs instead of many.
QA considerations
- Default selection is correct on first load.
- Reset returns to the default state, not to 'nothing selected'.
Limitations
- Slicer styling is limited compared with web components.
- Very long lists rely on search rather than pagination.
HTML prototype note
This interactive HTML example simulates the native Power BI behaviour. It is not Power BI itself and should not be interpreted as an implementation of the Power BI rendering engine.
UX designer defines
- Information hierarchy and column order
- Required fields and measures
- Default state (sort, filters, selection)
- Interaction intent and what it should affect
- Responsive priority and what may be dropped
- Accessibility expectations and focus order
- Empty, loading and error states
BI developer implements
- Dataset fields, measures and relationships
- Visual configuration in the format pane
- Filters, sort order and interaction wiring
- Drill-through / drill-down configuration
- Conditional formatting rules
- Row-level security and permissions
- Query performance optimisation
QA validates
- Data correctness against the source
- Correct default state on first load
- Sorting and filtering behaviour
- Drill and selection behaviour
- Permissions and row-level security
- Empty states and responsive layout
- Performance and export behaviour