Day 15: Filters & Interactions

Visual-level filters: apply only to one specific visual — set in the Filters pane with that visual selected. Page-level filters: apply to all visuals on the current page — set in the Filters pane with no visual selected, in the "Filters on this page" section. Report-level filters: apply to all visuals on all pages — set in the "Filters on all pages" section. Drillthrough filters: automatically applied when drilling through to a detail page. Row-level security filters: applied at the data model level based on user identity. Slicer filters: user-controlled filters via slicer visuals.

Format → Edit Interactions → select the slicer → for each visual, choose the interaction type: Filter (the slicer affects this visual), None (the slicer does not affect this visual). The None option removes the filter interaction completely — that visual will not respond to the slicer. Use this when: a summary KPI card should always show the total regardless of slicer selection, or when one slicer should affect a subset of visuals but not others.

Filters in the Filters pane are applied by the report developer — they restrict data for visuals without the user seeing or controlling them. Slicers are visible, interactive controls that the report user operates to filter data themselves. Use Filters for permanent restrictions (e.g. always exclude test orders). Use Slicers for user-controlled exploration (e.g. let users filter by Region or Year). From a DAX perspective, both create filter context — the mechanism is the same, the control point is different.

View → Sync Slicers. This opens the Sync Slicers pane. Select the slicer visual → the pane shows all pages with checkboxes for "Sync" (the slicer state is shared across pages) and "Visible" (whether the slicer appears on that page). Check "Sync" for all pages that should share the same filter state. When a user selects "North" on page 1, navigating to page 2 also shows North. You can have the slicer visible on some pages and invisible on others while still syncing its state — useful for a persistent filter that is set on one page and applied throughout.

ALL in a DAX measure removes filter context from specified columns or tables, overriding both page/visual filters AND slicer selections. If a user selects "North" in a Region slicer, Total Revenue = SUM(Sales[Revenue]) shows only North's revenue. But All Revenue = CALCULATE(SUM(Sales[Revenue]), ALL(Sales[Region])) shows the grand total regardless — the slicer has no effect on this measure. This is intentional — use ALL when you need a fixed denominator for percentage calculations. Use ALLSELECTED to override visual filters but still respect slicer selections.