Webbo3 Data Analysis Bootcamp · Power BI Module · Lesson 5

Advanced Report Design: Bookmarks, Navigation, Drill Through, Tooltips, Themes, and Publishing

A comprehensive lesson covering how to build interactive, professional-grade Power BI reports with bookmarks, navigation buttons, drill through pages, custom tooltips, themes, and cloud publishing for collaboration.

By now you have built basic Power BI reports with visuals, filters, and slicers. Those are the building blocks. This lesson is about the experience layer. A basic report shows data. An advanced report tells a story, guides the user through that story, and lets them explore deeper when they choose. Bookmarks let you save and replay report states. Navigation buttons turn a static canvas into an interactive application. Drill through pages let a manager click a bar in a chart and instantly see the underlying transactions. Custom tooltips reveal detail on hover without cluttering the main view. Themes enforce brand consistency across every visual. And publishing to Power BI Service transforms a desktop file into a live, shareable, collaborative asset that refreshes automatically. These are the skills that separate a report builder from a report designer. This lesson teaches you to design.

1. Bookmarks: Saving Report States

A bookmark in Power BI is a snapshot of the current state of a report page. It captures which visuals are visible, which filters are applied, which slicers are selected, the current sort order, and even the focus mode of individual visuals. Bookmarks let you build guided storytelling into your report. You can create a sequence of bookmarks that walk a user through a narrative: here is the overall picture, now here is the regional breakdown, now here is the problem area, now here is the recommended action. Users can click through bookmarks like slides, but unlike slides, the underlying data is live and interactive.

Creating a bookmark. First, configure your report page exactly as you want it to appear in the bookmark. Apply slicers, set filters, expand or collapse visuals, and select any drill levels. Then go to View → Bookmarks to open the Bookmarks pane. Click Add to create a new bookmark. Give it a descriptive name, for example "Overview - All Regions" or "Drilldown - Lagos Underperformance." Power BI saves the current state into the bookmark.

Bookmark options and properties. Each bookmark has configurable properties. Click the three dots next to a bookmark name in the Bookmarks pane. You will see options for Data, Display, and Current page. Data controls whether the bookmark saves the current filter and slicer selections. Display controls whether the bookmark saves the visibility state of visuals, for example if you have hidden certain charts to focus attention. Current page controls whether activating the bookmark jumps to the page where it was created. For storytelling sequences, you usually want all three enabled. For simple filter reset buttons, you might want only Data enabled.

Updating a bookmark. If you change the report state after creating a bookmark, you can update it without recreating it. Configure the page to the new desired state, right-click the bookmark in the Bookmarks pane, and choose Update. This overwrites the saved state with the current one. Be careful: there is no undo for bookmark updates. If you accidentally overwrite a carefully configured bookmark, you must recreate it manually.

Grouping bookmarks into stories. If you have many bookmarks, organize them into groups. In the Bookmarks pane, click the three dots and choose Group. Name the group, for example "Q1 Review Story" or "Executive Summary." Drag bookmarks into the group. Groups make it easier to manage complex reports and to present bookmarks in a logical sequence during meetings.

Bookmark limitations. Bookmarks do not capture cross-report states. They only work within the current report. They do not save personal bookmarks for individual users unless you are using Power BI Service and the user has permission to create personal bookmarks. Bookmarks also do not capture the state of custom visuals from the marketplace unless those visuals explicitly support bookmarking. Test every bookmark after creating it, especially on pages with complex custom visuals, to confirm it restores the intended state.

2. Buttons for Navigation Between Pages

A multi-page Power BI report without navigation buttons is like a website without links. Users must use the bottom tab bar, which is functional but unprofessional and confusing for non-technical audiences. Buttons turn your report into an application with a clear user journey. You can create home pages, detail pages, and back buttons that behave like a polished software interface.

Inserting a button. Go to Insert → Buttons and choose a button type. The blank button is the most flexible because you can customize it completely. Draw it on your canvas. With the button selected, go to the Format pane. Under Button text, type the label, for example "View Details" or "Back to Summary." Under Fill, choose a color that matches your theme. Under Border, add a subtle rounded border. Under Action, set the Type to Page navigation and select the destination page from the dropdown.

Button states and hover effects. A professional button has multiple states: default, hover, and pressed. In the Format pane, expand State and configure each state separately. For the default state, use your primary theme color with white text. For the hover state, use a slightly lighter or darker shade and consider adding a subtle shadow. For the pressed state, use a darker shade to simulate the button being clicked. These micro-interactions signal to the user that the element is clickable and provide visual feedback that the system is responding. Without state changes, buttons look static and users may not realize they are interactive.

Icon buttons for visual navigation. Instead of text labels, you can use icon buttons for a cleaner look. Power BI includes a built-in icon library under Insert → Buttons. Choose icons like a home symbol, an arrow, a magnifying glass, or a chart. Format the icon color to match your theme. Set the action to page navigation or bookmark navigation. Icon buttons work best in a consistent navigation bar placed at the top or left edge of every page. Align them precisely using the position and size properties in the Format pane, or by multi-selecting and using the alignment tools under Format → Align.

Bookmark navigation buttons. Buttons can also trigger bookmarks instead of jumping to pages. This is how you build the storytelling experience. Create a button labeled "Next Insight" and set its action to a bookmark. Create another labeled "Previous Insight" and set it to the previous bookmark in your sequence. Users click through a guided narrative without leaving the page. This is powerful for executive presentations where you want to control the pacing and focus attention on one insight at a time.

Consistent navigation across all pages. The most professional reports have identical navigation elements on every page. After designing your navigation bar on the first page, select all navigation buttons, copy them with Ctrl + C, navigate to each other page, and paste with Ctrl + V. Position them in the exact same coordinates. This consistency reduces cognitive load for users. They always know where to find the home button, the back button, and the filter reset button because those elements never move.

3. Drill Through Pages: Deep Dive on a Data Point

Drill through is one of the most powerful features in Power BI. It lets a user right-click a data point in a visual, for example a bar representing Lagos sales, and choose an option that jumps to a dedicated detail page filtered to that specific data point. The detail page shows granular information: individual transactions, customer lists, product breakdowns, or trend lines for that specific entity. This transforms a high-level summary report into an interactive exploration tool.

Creating a drill through page. Create a new report page and name it something descriptive, for example "Store Detail" or "Product Breakdown." This page will serve as the destination when users drill through from a summary visual. On this page, add visuals that show detail-level data: a table of transactions, a trend line chart, a map of store locations, or KPI cards specific to the drilled entity. Design the page as if it were a standalone report for one specific item, because that is exactly what it becomes when filtered.

Setting up the drill through field. In the Fields pane, drag the field you want users to drill through on into the Drill through well. This well is located in the middle of the Visualizations pane, between the filters area and the visual types. For example, if you want users to drill through from a bar chart of regions to a detail page, drag the Region field into the Drill through well. Power BI automatically creates a back button on the drill through page. You can customize this button or replace it with your own navigation design.

Using drill through from a visual. On your summary page, create a visual that includes the field you placed in the Drill through well. For example, a column chart of sales by region. Right-click any bar in the chart. In the context menu, you will see an option that says "Drill through" followed by your page name, for example "Drill through → Store Detail." Click it. Power BI jumps to the Store Detail page and automatically filters every visual on that page to the region you clicked. If you clicked the Lagos bar, the detail page shows only Lagos data. The filter is passed dynamically and works for any data point in the source visual.

Drill through with multiple fields. You can place multiple fields in the Drill through well. For example, Region and Product Category. Users can then drill through from any visual that contains either field. If a visual contains both fields, the user can choose which one to pass as the filter. This flexibility is useful when you have summary pages at different granularities and want one detail page to serve multiple entry points.

Keep all filters and cross-highlight. In the Drill through settings, accessible from the page settings or the three dots on the drill through field, you can choose whether to keep the current filters when drilling through. If enabled, the detail page inherits not only the drill through filter but also any slicers or filters the user had active on the summary page. This preserves context. If disabled, the detail page shows only the drilled entity with all other filters cleared. Choose based on whether the user journey benefits from preserved context or needs a clean slate.

Drill through versus drill down. Do not confuse drill through with drill down. Drill down is a feature within a single visual where you click a down arrow to see more granular categories within the same visual, for example from year to quarter to month. Drill through jumps to an entirely different page with different visuals. Both are useful, but they serve different purposes. Drill down explores hierarchy within one chart. Drill through explores detail across many charts on a dedicated page.

4. Custom Tooltips

The default tooltip in Power BI is a small box that appears when you hover over a data point, showing the measure value and any tooltips you have configured in the field well. It is functional but limited. Custom tooltips let you design an entire report page that appears as a tooltip, complete with multiple visuals, images, and conditional formatting. This turns a simple value display into a rich contextual preview.

Creating a tooltip page. Create a new page and name it descriptively, for example "Product Tooltip" or "Region Tooltip." In the Format pane for the page, expand Page information and set Tooltip to On. This marks the page as a tooltip rather than a regular report page. Resize the page to an appropriate tooltip size. The default tooltip page size is small, around 320 by 240 pixels, but you can customize it. A good tooltip is large enough to show a mini chart and a few KPIs, but small enough that it does not obscure the main visual.

Designing the tooltip content. Add visuals to the tooltip page just like any other page. A typical custom tooltip contains a small line chart showing the trend for the hovered item, a card showing the current value, and maybe a small bar chart comparing the item to the overall average. Because the tooltip inherits the filter context from the data point being hovered, every visual on the tooltip page automatically filters to that specific data point. If you hover over the Lagos bar in a regional sales chart, the tooltip shows Lagos trend, Lagos current value, and Lagos versus average.

Assigning the tooltip to a visual. Select the visual on your main report page that should display the custom tooltip. In the Format pane, expand Tooltip. Change the Type from Auto to Report page. Select your tooltip page from the dropdown. Now when you hover over any data point in that visual, your custom tooltip page appears instead of the default tooltip box.

Tooltip best practices. Keep tooltips focused. One mini trend chart, one KPI card, and one comparison metric is usually enough. Avoid cramming a full dashboard into a tooltip. Users hover for a quick insight, not an exhaustive analysis. Use consistent colors and fonts with your main report so the tooltip feels like a natural extension, not a foreign object. Test tooltips on different screen sizes. A tooltip that looks perfect on a large monitor might overflow or truncate on a laptop screen.

Conditional tooltip visibility. You can control whether a tooltip appears based on a measure. Create a measure that returns 1 when the tooltip should show and 0 when it should not. In the tooltip page settings, set a filter using this measure. This is advanced but useful for suppressing tooltips when data is insufficient or sensitive. For example, you might hide tooltips for regions with fewer than ten transactions to avoid revealing individual customer details.

5. Report Themes and Templates

A professional report does not look like it was built by five different people. Colors, fonts, and visual styles should be consistent across every page. Manually formatting each visual is tedious and error-prone. Themes let you define a master style once and apply it everywhere. Templates let you start new reports from a pre-designed foundation rather than a blank canvas.

Creating a custom theme. Go to View → Themes → Customize current theme. This opens a dialog where you can set the primary color, secondary color, sentiment colors for positive and negative values, structural colors for headers and backgrounds, and text defaults for titles, labels, and values. Choose colors that match your organization's brand guidelines. If you do not have brand guidelines, use a professional palette generator like Coolors or Adobe Color, export the hex codes, and paste them into the theme dialog.

Theme JSON for advanced control. The Customize current theme dialog covers basics, but for full control over every visual type, you need a JSON theme file. Create a JSON file with the .json extension and define properties for each visual type: page, text box, card, gauge, KPI, slicer, table, matrix, and so on. You can specify exact font families, font sizes, border styles, background colors, and conditional formatting rules. Save the file and import it via View → Themes → Browse for themes. Microsoft provides a theme generator tool and sample JSON files in the Power BI documentation. Start with a sample and modify it rather than writing JSON from scratch.

Applying themes across reports. Once you have a theme file, apply it to any report by browsing for the theme file. All visuals in the report update to match the theme instantly. This is how large organizations enforce brand consistency. The analytics team maintains one master theme file, and every report creator applies it at the start of a new project. If the brand colors change, update the JSON file and reapply it. Every report updates in minutes instead of hours of manual reformatting.

Report templates. A template is a Power BI file with data connections removed but all visuals, themes, bookmarks, and navigation preserved. Save a finished report as a template via File → Export → Power BI template. When you open a template, Power BI prompts you to connect to your own data source. The visuals and layout remain, but they populate with your data. Templates are invaluable for recurring reports. If your team produces a monthly sales report with the same structure every time, create a template once and reuse it. This eliminates the setup phase and ensures every monthly report has identical formatting and navigation.

Theme and template limitations. Themes control visual styling but not layout. A theme changes colors and fonts, but it does not move visuals or resize them. Templates preserve layout but require the new data source to have the same or similar column names. If your template expects a column named Sales_Amount and your new data source names it Revenue, the visuals will show errors until you remap the fields. Always test a template with a new data source before distributing it to your team.

6. Publishing to Power BI Service

Power BI Desktop is where you build. Power BI Service is where you publish, share, and collaborate. A report that lives only on your laptop is not a business asset. It is a draft. Publishing makes your report accessible to stakeholders, enables automatic data refresh, and unlocks collaboration features like comments, sharing, and embedding.

Signing in and workspaces. Before publishing, sign in to Power BI Desktop with your organizational account. Go to File → Account → Sign in. You need a Power BI Pro or Premium Per User license to publish to most workspaces, though some organizations have Premium capacity that allows free users to consume content. A workspace is a container in Power BI Service where reports, datasets, and dashboards are stored. Think of it as a shared folder. Create a workspace via the Power BI Service web interface, app.powerbi.com, and name it after your team or project, for example "Webbo3 Sales Analytics."

Publishing a report. In Power BI Desktop, click the Publish button in the top ribbon. Select the destination workspace from the list. Power BI uploads the report file and the dataset to the Service. A success dialog appears with links to open the report in Power BI Service. Click the link to verify that everything published correctly. Check that visuals render, filters work, and drill through pages function as expected. Sometimes custom visuals from the marketplace do not render in Service until the administrator approves them. Test this immediately after publishing.

Configuring scheduled refresh. After publishing, your report needs to stay current. Go to the Power BI Service web interface, navigate to your workspace, click the dataset name, and choose Settings → Scheduled refresh. Configure the refresh frequency: daily, weekly, or multiple times per day depending on your license. Enter the data source credentials if required. For on-premises data sources, install and configure the On-premises data gateway on a server in your organization. The gateway acts as a secure bridge between your internal databases and Power BI Service in the cloud. Without it, Power BI cannot reach databases behind your company firewall.

Setting up row-level security in Service. If your report contains sensitive data that different users should see differently, for example regional managers should only see their own region, configure row-level security (RLS) in Power BI Desktop before publishing. Define roles and DAX filters in the Modeling tab. After publishing, assign users to roles in the dataset settings in Power BI Service. When a user opens the report, they see only the rows permitted by their role. This is essential for compliance and data privacy. Test RLS thoroughly by using the View as roles feature in Desktop and by having colleagues in different roles verify their views in Service.

Creating dashboards from report pages. In Power BI Service, you can pin live tiles from multiple reports to a single dashboard. Dashboards are not editable in the same way as reports. They are static collections of tiles that update when the underlying report refreshes. To create a dashboard, open a published report, hover over a visual, click the pin icon, and choose an existing dashboard or create a new one. Dashboards are useful for executive overviews that combine KPIs from several reports into one at-a-glance view. They do not support slicers or drill through, so use them for monitoring, not for analysis.

7. Sharing and Collaboration Basics

A published report is only valuable if the right people can access it. Power BI Service provides several sharing mechanisms, each with different permissions and use cases. Choosing the right one matters for security, governance, and user experience.

Direct sharing. In Power BI Service, open a report and click Share in the top-right. Enter email addresses or security groups. Choose whether recipients can reshare the report, build content with the underlying dataset, or receive access to the underlying dataset. Direct sharing is fast and simple, suitable for small teams and ad-hoc requests. It is not scalable for large organizations because tracking who has access to what becomes impossible.

App distribution. For broader distribution, package your reports and dashboards into an App. In your workspace, click Create app in the top-right. Configure the app navigation, add descriptions, and choose which content to include. Set permissions: who can access the app, and whether they can view only or also build content. Publish the app. Users receive a notification and can find the app in their Apps list. Apps are the standard distribution method for organizational reporting because they provide a curated experience, controlled permissions, and easy updates. When you update the underlying reports, republish the app, and all users see the new version automatically.

Collaboration with comments and annotations. In Power BI Service, users can add comments to specific visuals or to the entire report. Click the Comments button in the top bar. Type a comment, optionally @mention a colleague to send a notification, and click Post. Comments are threaded and preserved across sessions. They are visible to everyone with access to the report, making them ideal for asynchronous review workflows. A manager can leave a question on a declining trend line, the analyst can reply with context, and the entire conversation is attached to the visual for future reference.

Alerts on data. Users can set data alerts on card visuals and KPI tiles in dashboards. Click the ellipsis on a card, choose Manage alerts, and set a threshold. For example, alert me when monthly revenue drops below ten million naira. When the data refreshes and crosses the threshold, Power BI sends an email notification. This is how you turn passive reporting into active monitoring. Alerts are personal to the user who sets them and do not affect other viewers.

Embedding reports in other applications. For the most integrated experience, embed Power BI reports into SharePoint, Teams, or custom web applications. In Power BI Service, open a report, click File → Embed, and choose the embedding option. SharePoint and Teams embedding require minimal configuration. Custom embedding using the Power BI REST APIs requires developer resources but gives you full control over the user interface and authentication flow. This is how organizations build data-driven applications where Power BI visuals live inside their own software.

Using AI to Move Faster in Advanced Report Design

Advanced report design involves many repetitive tasks: formatting buttons, aligning navigation elements, writing DAX for drill through filters, and configuring JSON theme files. AI can handle much of this mechanical work, letting you focus on the user experience and data story.

1. Generate DAX measures for drill through and tooltip context.
Drill through pages often need measures that behave differently depending on the filter context. For example, a detail page might need a measure that shows "Sales for selected region" as a dynamic title. Writing this DAX requires understanding the SELECTEDVALUE function. Ask Copilot: "Write a DAX measure that returns the name of the currently selected region for use in a card visual title on a drill through page. If multiple regions are selected, return 'Multiple Regions'." The AI will generate something like Selected Region = IF(HASONEVALUE(Regions[Region]), VALUES(Regions[Region]), "Multiple Regions"). Test it on your drill through page, verify it updates when you drill through from different bars, and adjust the fallback text to match your style guide.

2. Use AI to write and validate theme JSON files.
Theme JSON is verbose and easy to break with a missing comma or bracket. Describe your brand colors and visual requirements to an AI assistant: "Create a Power BI theme JSON file with primary color #0a6e6e, secondary color #c98a3e, positive green #28a745, negative red #dc3545, font Calibri, and rounded corners on all cards." The AI will generate a complete JSON structure. Paste it into a text editor, save as .json, and import into Power BI. If visuals do not update as expected, paste the JSON back into the AI and ask: "This theme JSON is not applying card corner radius correctly. What is wrong?" AI can spot syntax errors or missing visual type definitions faster than manual inspection.

3. Design navigation UX with AI-generated wireframes.
Before building buttons and bookmarks, sketch the user flow. Describe your report structure to an AI image generator or design assistant: "I need a wireframe for a three-page Power BI report with a top navigation bar, a home page with four KPI cards and a trend chart, a detail page with a table and map, and a settings page with slicers. The navigation should have home, back, and filter reset buttons." Use the wireframe as a blueprint when you build in Power BI. This prevents the common mistake of starting to drag visuals onto the canvas without a plan, which leads to cluttered, inconsistent layouts.

4. Generate documentation for published reports.
Every report published to Power BI Service should have documentation: data sources, refresh schedule, owner contact, and known limitations. This is tedious to write but essential for governance. Ask Copilot: "Draft a one-page documentation template for a Power BI report named 'Regional Sales Dashboard' that sources data from SQL Server, refreshes daily at 6 AM, uses row-level security for regional managers, and has drill through to store detail pages. Include sections for data sources, refresh schedule, security model, and support contact." Customize the draft with your specific details and publish it alongside the report in your workspace. This is how professional analytics teams operate.

5. Verify AI-generated DAX and JSON before deploying.
AI can generate syntactically correct DAX that returns logically wrong results. A measure for tooltip conditional visibility might use COUNTROWS when it should use DISTINCTCOUNT. A theme JSON might define a color for dataLabels but not for categoryLabels, leaving some text unstyled. Always test AI-generated code in a development workspace before publishing to production. Create a test page with every visual type, apply the theme, and check every element. Drill through from every entry point. Hover over every visual to verify tooltips. The time spent testing is less than the time spent explaining to stakeholders why a published report looks broken.

A habit worth building from this lesson onward: for every advanced feature you add to a Power BI report, bookmarks, drill through, custom tooltips, or themes, document what you built and why. Use AI to draft that documentation, but verify every technical detail yourself. A report that is beautiful but undocumented becomes a liability when you leave the team or when a stakeholder asks how a number is calculated six months later. Design for maintainability, not just for the demo.

Next lesson: DAX optimization, query folding, and performance tuning for large datasets.