Filters & slicers
Filters are part of the reading experience, not chrome. The user must always be able to see what is filtered and undo it in one action.
Filter panel pattern
Left filter rail, context bar, filtered content
Simulation of native Power BI behaviour
Filter contextAll data (no filters applied)
RegionAll
DepartmentAll
ChannelAll
Week (between slicer)
W1–W13
Revenue by department
FreshBeveragesGroceryNon-foodHousehold
Revenue by store
| vs Budget | ||||
|---|---|---|---|---|
| Eindhoven | €1.7M | €1.7M | €411k | ▼ -1.1% |
| Groningen | €1.2M | €1.2M | €302k | ▼ -1.9% |
| Amersfoort | €1.2M | €1.2M | €291k | ▼ -0.5% |
| Rotterdam | €986k | €999k | €248k | ▼ -1.3% |
| Den Haag | €911k | €923k | €227k | ▼ -1.3% |
| Utrecht | €900k | €906k | €223k | ▼ -0.7% |
| Arnhem | €899k | €903k | €225k | ▼ -0.4% |
| Nijmegen | €679k | €687k | €170k | ▼ -1.1% |
| Total | €8.4M | €8.5M | €2.1M | -1.0% |
8424 of 8424 fact rows are in scope. Empty results are a design state: say what was filtered and offer the reset.
Designer
Order slicers by how often they are used, not alphabetically.
Use tile slicers for 2–5 mutually exclusive values, dropdown above ~15 values.
Specify default selections and whether they persist across pages.
Developer
Slicer visual ▸ Selection controls for single/multi-select and “Select all”.
Sync slicers pane controls cross-page behaviour and visibility per page.
Bookmark with “Data” captured provides the reset-all-filters action.
Power BI limitation
Slicers cannot be collapsed into a native drawer; a filter panel is built with a bookmark and a shape. The built-in filter pane can be styled but not restructured.