7.4 Report Page Configuration and Slicers

Quick Answer: Slicers are interactive filter controls. Key types: list (checkboxes), dropdown, range (between), relative date ("last 30 days"), and hierarchy. Sync slicers to share filtering across pages. Configure visual interactions (Format > Edit Interactions) to control how clicking one visual affects others.

Slicers

Configure single vs. multi-select (hold Ctrl to multi-select in single-select mode), enable a search box for long lists, and show/hide Select All. A relative date slicer (set, for example, to "Last 30 Days") recalculates against today's date automatically, so the dashboard never needs manual date updates, ideal for always-current views.

Sync Slicers

View > Sync slicers lets one slicer control filtering on multiple pages.

A common pattern: a Year slicer visible on Page 1 that syncs (but is hidden) on Pages 2-5, so every page filters to the same year while the control shows only once.

Visual Interactions

Select a visual, then Format > Edit interactions, and choose how it affects each other visual.

Defaults: charts Highlight; tables, matrices, and maps Filter; slicers always Filter. Set None when a KPI card should always show the total regardless of selections; set Filter for strict drill-down between related visuals; keep Highlight for exploratory dashboards where context matters.

Filter Pane

You can lock filters (users cannot change them), hide them while keeping them active, require single selection, and search within values. A visual-level filter overrides the page-level filter for that one visual.

Page Configuration

Page settings also control background color/image and transparency, and navigation via the page navigator button bar, custom buttons with actions, and bookmarks that save page state (filters, selections, visibility) for guided storytelling. Under report settings you can allow or deny export to PDF, PowerPoint, and image, and control copying or exporting underlying data.

On the Exam

The PL-300 tests choosing the correct slicer type, configuring sync slicers across pages, setting visual interactions (Filter/Highlight/None), the filter-pane levels (visual/page/report), and the difference between filter and highlight.

Pages Are Designed Experiences, Not Just Canvases

Report-page configuration is where a model becomes a usable product. The decisions, which slicers, how visuals interact, what the filter pane exposes, how pages are sized and navigated, determine whether a business user can answer their questions without confusion. The PL-300 "create reports" objective tests these choices directly, so you should be fluent in the trade-offs: a dropdown slicer to save space versus a list slicer for visibility, a relative-date slicer for an always-current view versus a fixed range for a point-in-time report, and sync slicers to keep multipage reports coherent.

Visual Interactions Are the Heart of Interactivity

The default cross-filtering behavior, click a bar and watch related visuals respond, is powerful but must be shaped deliberately. Charts default to Highlight, while tables, matrices, and maps default to Filter, and slicers always filter. Setting an interaction to None is the standard fix when a KPI card or total should stay constant regardless of selections; setting Filter enforces strict drill-down between related visuals; keeping Highlight preserves context for exploratory dashboards.

Recognizing which interaction a described behavior requires, "the total should not change when I click a bar" implies None, is a high-frequency exam pattern.

Filter Scopes and Sync Compose Cleanly

The filter pane's three scopes layer predictably: report-level filters apply everywhere, page-level filters refine a single page, and visual-level filters refine one visual on top of the broader scopes. Filters combine (narrower refines broader) rather than fighting, so a visual-level filter takes effect within whatever report-level filter is active. Sync slicers add a second axis of control by separating which pages a slicer affects (Sync) from which pages it appears on (Visible), enabling the common "one Year slicer visible on the landing page but driving every page" design.

Understanding how scopes and sync compose lets you predict the data each visual will show, which is exactly what the configuration questions ask.

Bookmarks, Buttons, and Guided Navigation

Beyond slicers and interactions, polished reports use bookmarks and buttons to script an experience. A bookmark captures the current page state, applied filters, slicer selections, the visible/hidden set of visuals, and the current spotlight, so you can build toggles (switch a visual between chart and table), reset-filter buttons, and step-through narratives. Pairing bookmarks with the selection pane (to show and hide specific visuals) and buttons (with navigate or bookmark actions) lets one canvas serve several views without crowding.

The page navigator auto-generates a button bar across pages, and custom buttons can deep-link to a specific page or apply a bookmark. These tools, together with page size presets and backgrounds, are how you turn a set of visuals into a coherent, navigable application, and the exam expects familiarity with what each mechanism does and when to choose it.