Skip to content
FR

Report Usability and Storytelling

Step 17 of 24

Report Usability and Storytelling

Introduction

This lesson continues the domain Visualize and analyze the data (25–30% of the PL-300 skills measured, outline dated April 20, 2026). Under "Enhance reports for usability and storytelling" the official outline covers: configuring bookmarks, creating custom tooltips, editing and configuring interactions between visuals, configuring navigation (page navigator, buttons, drillthrough), applying sorting, configuring sync slicers, grouping and layering objects with the Selection pane, drilling down with interactive visuals, configuring export settings, designing reports for mobile, enabling personalized visuals, designing apps, configuring subscriptions and data alerts, and accessibility (alt text, tab order, titles, themes). Microsoft does not publish the number of questions or the question-type mix; OnLevelUp mock exams use a 50-question practice length and an 80% practice target, neither of which is official nor equal to the 700/1000 passing score.

After this lesson you will be able to design a report that guides a reader from summary to detail, choose between bookmarks, drillthrough and tooltips, control cross-filtering, and make the report accessible and usable on a phone.

Learning objectives

  • Configure drill down, drill up, expand, and drillthrough, and tell them apart.
  • Create and use bookmarks, buttons and the Selection pane to build toggles and navigation.
  • Build a report-page tooltip and a drillthrough page.
  • Edit interactions and configure sync slicers across pages.
  • Apply sorting, including "sort by column", to categorical and date axes.
  • Configure accessibility: alt text, tab order, titles, contrast, keyboard navigation.
  • Design a phone layout and configure export settings, personalized visuals, subscriptions and alerts.

1. Drilling and exploring: five different mechanisms

Exam questions often hinge on picking the right navigation mechanism.

Mechanism What it does Setup
Drill down / up Moves through levels of a hierarchy inside one visual (Year → Quarter → Month) Add several fields to the axis (or a hierarchy), turn on drill mode with the down-arrow icon
Expand all one level Shows the next level for every item at once, keeping the parent in the label Fork icon in the visual header
Go to the next level Replaces the parent level with the next level for all items Double-arrow icon
Drillthrough Jumps to another page filtered by the selected item, for example a Product details page Put the field in the Drill through well of the target page; the reader right-clicks a data point
Cross-filter / cross-highlight Selecting a point filters or highlights other visuals on the same page Default behaviour, controlled by Edit interactions

Drillthrough details: the target page can keep all filters (a switch in the drillthrough well), can be a page in another report (cross-report drillthrough, enabled on both reports), and Power BI adds an automatic Back button. A drillthrough page can be hidden from the page tabs so that it is reachable only by drilling.

Hierarchies and dates. A date column gives Year, Quarter, Month and Day through auto date/time or a hand-built hierarchy on a date table. Prefer a proper date table (lesson 4) so that month names sort in calendar order.

Worked example: a drillthrough page for product returns

Scenario. A sales report page shows returns by product category. Managers want to right-click a category and see a detail page with returns by reason, store and month, showing only that category. The detail page must not appear as a tab.

Step 1. Add a new page called Return details. Add a bar chart of returns by reason and a matrix by store and month.

Step 2. In the Visualizations pane, drag DimProduct[Category] into the Drill through → Add drill-through fields here well. Leave Keep all filters on if the date slicer from the source page should carry over.

Step 3. Right-click the page tab and choose Hide page.

Step 4. On the source page, right-click a category bar and choose Drill through → Return details. The target page is filtered to that category and shows a Back button.

Why not the alternatives. A bookmark cannot pass the selected category as a filter. Drill down stays inside one visual and cannot reveal reasons and stores side by side. A page tooltip appears only on hover and cannot host a matrix the manager can study.

2. Bookmarks, buttons, and the Selection pane

A bookmark captures the state of a report page: filters, slicer selections, sort order, visible/hidden objects, drill location, and optionally the current page. Create one from View → Bookmarks → Add. Each bookmark has options: Data (filters and slicers), Display (visibility, spotlight), Current page, and a selected visuals scope.

The Selection pane lists every object on the page. You can show or hide objects with the eye icon, rename them, reorder layers (z-order) and group objects. Bookmarks plus the Selection pane let you build:

  • View toggles: a button that swaps a chart for a table (bookmark A shows the chart and hides the table, bookmark B does the opposite).
  • Reset filters: a button linked to a bookmark captured with default slicers.
  • Slide-in panels: a hidden filter panel revealed by a button.
  • Story steps: a presentation of bookmarks in order (View → Bookmarks → View plays a slideshow).

Buttons and shapes can have actions: Back, Bookmark, Page navigation, Q&A, Web URL, Drillthrough, Apply all slicers, Clear all slicers. A page navigator visual creates tabs automatically from the report's pages and can hide hidden pages. A button's text or colour can be driven by a DAX measure through conditional formatting, but the action target itself is chosen statically.

Bookmarks differ from drillthrough: a bookmark restores a preconfigured state; drillthrough passes the selected item as a filter to another page. Personal bookmarks (the reader's own) are separate from the author's report bookmarks.

Pitfalls. If a bookmark is captured with Data off, selecting it will not reset slicers or filters. When a bookmark should only change visibility, turn Data off and keep Display on. A visual hidden through the Selection pane is still part of the report: do not use hiding as a security measure; use row-level security.

3. Interactions and sync slicers

By default, selecting a data point in one visual cross-filters most visuals and cross-highlights others (highlighting dims the non-selected part of a column). In Format → Edit interactions, each target visual displays three icons: Filter, Highlight, None. Examples:

  • Stop a KPI card from changing when a bar is clicked: set the card to None.
  • Make a column chart filter rather than highlight: set Filter.

Interactions are set per source visual: switching them off for one slicer or chart must be repeated for each source if wanted.

Sync slicers (View → Sync slicers pane) synchronize a slicer selection across pages and control whether the slicer is also visible on each page. The same slicer can be synced to pages A, B and C while appearing only on A. Sync works for the same field (or a field in a shared group); slicers on different fields are independent. A slicer can also be sorted, single or multi-select, offer Select all, or include Search.

Page-level and report-level filters (lesson 8) combine with slicers using AND. An Apply all slicers button lets readers pick several values before the report queries the model, a good pattern for large DirectQuery models.

4. Custom tooltips and sorting

A report page tooltip is a small page, sized as Tooltip, with Allow use as tooltip turned on. It takes the context of the hovered data point: add a visual and Power BI filters it by the hovered category. To use it, select the target visual, set Tooltip → Type: Report page and choose the page. Use it for a trend line under each bar or a details card. Keep tooltip pages light (they render on hover) and hide them from page tabs.

Default tooltips can also include extra fields from the Tooltips well, with no page needed. Modern tooltips with a drill footer (generally available since January 2026) let readers drill from the tooltip.

Sorting. A text column such as Month Name sorts alphabetically (April before January). Fix this in the model with Sort by column (Month Name sorted by Month Number). In a visual you can sort the axis by the category or by a measure, ascending or descending. If sorting a date axis seems to have no effect, check whether the axis is continuous rather than categorical.

Worked example: month names in calendar order

Scenario. A column chart of revenue shows months as April, August, December, February, and sorting the chart ascending leaves it alphabetical.

Step 1. In Data view or Model view select DimDate[MonthName].

Step 2. Column tools → Sort by column → MonthNumber.

Step 3. Return to the chart and sort the axis by MonthName ascending. Months now follow the calendar.

Why other choices are worse. Sorting by the revenue measure orders by value, not calendar. Converting MonthName to a number loses readable labels. A custom visual is unnecessary: the fix belongs in the model, so every visual benefits.

5. Accessibility and consistency

Power BI supports reports readable by people using screen readers, keyboards or high contrast. Expected skills:

  • Alt text for every informative visual (Format → General → Alt text). Decorative shapes can be left without alt text.
  • Tab order: the Selection pane's tab-order option sets the keyboard sequence. Put it in logical reading order and remove purely decorative items.
  • Titles and labels: meaningful visual titles stating the finding ("Returns up 12% in Q3"), axis titles, data labels where values matter.
  • Contrast and colour: do not encode meaning by colour alone; add markers, patterns or labels. Choose a theme with accessible contrast or a colour-blind-friendly palette.
  • Keyboard navigation: readers can reach visuals, the filter pane and the visual header with the keyboard.
  • Show as a table: readers can view a visual's data as a table (a screen-reader-friendly alternative).
  • High contrast support through Windows themes.

Consistency also matters for storytelling: the same colour for the same meaning, an aligned grid, a clear top-left starting point, concise titles and whitespace. Use one page per question and avoid scrolling.

6. Mobile, export, personalization, subscriptions, alerts

Phone layout. In Desktop choose View → Mobile layout and drag visuals onto a vertical canvas. Visuals not placed on the canvas are not displayed in the phone layout. Choose the key cards and slicers first and use a single column. The mobile layout does not change the desktop report.

Export settings. In File → Options and settings → Report settings you can control what readers may export: summarized data only, summarized and underlying data, or no export. Tenant admin settings can override this, and sensitivity labels with encryption may restrict exports.

Setting Effect
Export data: none No "Export data" command for the report's visuals
Summarized only Data as shown in the visual
Summarized + underlying Includes underlying rows (needs build or edit permission)

Personalized visuals. When enabled in report settings, readers can change the visual type, add or remove fields and apply their own changes (saved per reader) without edit permission.

Subscriptions. Users subscribe to a report page or dashboard and receive an email snapshot on a schedule (or after a data refresh). Paginated report subscriptions can deliver a PDF or other formats. Subscription availability depends on licensing and workspace capacity.

Data alerts. Alerts are set on dashboard tiles for card, gauge and KPI visuals in the service. Power BI notifies the user in the service and mobile app, and optionally by email, when the value crosses a threshold. They are not set on report visuals or on bar-chart tiles. In Fabric, Data Activator can trigger richer actions from report visuals.

Q&A and Copilot. The Q&A visual lets readers type natural-language questions answered against the semantic model; synonyms and the linguistic schema affect accuracy. Microsoft has announced that the legacy Q&A experience will be deprecated in December 2026, and its newer natural-language features are built on Copilot, whose availability depends on capacity and tenant settings. Always check AI-generated text before sharing.

Apps. A Power BI app packages reports and dashboards for audiences, with navigation and permissions (lesson 11).

7. Pitfalls and exam tips

  • Drillthrough vs drill down vs bookmark: a page jump with the selected item is drillthrough; a hierarchy in one visual is drill down; a saved state is a bookmark.
  • Bookmark not resetting slicers: the bookmark's Data setting was off.
  • Tooltip page appears as a tab: hide it and turn on Allow use as tooltip.
  • Slicer on page 1 not filtering page 2: use Sync slicers.
  • Alerts on a table visual: not possible; only card, gauge and KPI tiles on dashboards.
  • A hidden visual is not secure: use RLS, not the Selection pane.
  • Months out of order: Sort by column in the model.
  • Exam tip: identify the reader's goal (explore a hierarchy, jump to details, toggle views, get an alert) and map it to the exact feature.

8. Mini case study

Situation. Contoso Retail's operations report has a map of stores, a revenue-by-category bar chart, a KPI for on-time delivery, and a table of orders. Requirements: (1) clicking a store in the map must not change the KPI; (2) right-clicking a category must open a detailed, hidden page; (3) a button must switch the table between orders and returns; (4) store managers on phones see only the KPI and a store slicer; (5) a manager wants a phone alert when on-time delivery falls below 92%; (6) screen-reader users must hear visuals in reading order.

Question. Which features implement each requirement?

Solution, commented.

  1. Edit interactions: select the map and set the KPI to None.
  2. Drillthrough: create a hidden Category details page with Category in the Drill through well.
  3. Two bookmarks and buttons: place each table in the Selection pane, make one visible per bookmark with Data off and Display on, and assign the buttons to the bookmarks.
  4. Mobile layout: place only the KPI and the slicer on the phone canvas.
  5. Data alert: pin the KPI to a dashboard and add an alert on the tile in the service with threshold 92.
  6. Alt text and tab order: add alt text and set the tab order in the Selection pane.

Why not the alternatives. A bookmark cannot filter by the clicked category. An alert on a report visual is not available. Hiding one table through the Selection pane without bookmarks gives the reader no way to switch.

Key terms

  • Drillthrough: navigation to a target page filtered by the selected item.
  • Bookmark: saved report state (filters, visibility, page).
  • Selection pane: list of page objects with visibility, grouping and tab order.
  • Sync slicers: keep one slicer's selection across pages.
  • Report page tooltip: hover page filtered by the data point.
  • Sort by column: model setting giving another column's order to a text column.
  • Data alert: threshold notification on a dashboard card, gauge or KPI tile.
  • Personalized visuals: reader-level changes to visuals.
  • Alt text: text description for screen readers.

Summary checklist

  • I can pick between drill down, drillthrough, bookmarks and tooltips.
  • I can build view toggles and a reset button with bookmarks and the Selection pane.
  • I can edit interactions and sync slicers.
  • I can fix sort order with Sort by column.
  • I can apply alt text, tab order and accessible colours.
  • I can design a phone layout and set export and personalization options.
  • I know where alerts and subscriptions are configured and their limits.

Official sources