Use buttons to navigate between pages in Power BI

Use buttons to navigate between pages in Power BI

Overview

Power BI restricts third-party applications from directly controlling page navigation. To address this limitation, there is a recommended approach that uses native Power BI buttons to achieve consistent and reliable navigation.

Buttons allow report authors to create application-style navigation in Power BI reports. Instead of relying on page tabs, users can move between report pages using clearly labeled buttons such as Home, Sales, or Finance.

This approach improves usability, supports guided workflows, and enables consistent navigation across complex Power BI applications.

This article describes how to create and configure navigation buttons step by step.


Before you begin

Ensure that:

  • Your report pages are clearly named

  • You understand which pages act as landing pages and which are detail pages

  • Power BI Desktop is updated to a recent version


Step 1: Organize and name report pages

  1. In Power BI Desktop, review the Pages pane at the bottom of the report.

  2. Rename pages using clear, user-friendly names.

Example page structure:

  • Home

  • Sales Overview

  • Sales Detail

  • Finance

  • Operations

Page names are used as navigation destinations and should reflect user intent.


Step 2: Insert a button

  1. Select Insert from the ribbon.

  2. Choose Buttons.

  3. Select a button type (for example, Blank).

The button is added to the report canvas.


Step 3: Configure the button action

  1. Select the button.

  2. In the Format pane, expand Action.

  3. Set Action to On.

  4. Configure the following:

    • Type: Page navigation

    • Destination: Select the target page

When users click the button in reading mode, they will be navigated to the selected page.


Step 4: Add button text

  1. With the button selected, expand Text in the Format pane.

  2. Set Text to On.

  3. Enter a label that matches the destination page (for example, Home or Sales).

  4. Adjust text size, alignment, and padding as needed.

Use short, descriptive labels for clarity.


Step 5: Duplicate buttons to build navigation

  1. Copy the button (Ctrl+C) and paste it (Ctrl+V).

  2. Update the Action → Destination for the new button.

  3. Update the button text.

Repeat this process to create a full navigation menu.

Tip
Use the Selection pane (View → Selection) to rename buttons and keep navigation elements organized.


Step 6: Create a Back or Home button

Power BI does not provide a global “Back” button, but you can simulate navigation using page navigation.

Create a Home button

  1. Insert a button.

  2. Enable Action.

  3. Set Type to Page navigation.

  4. Set Destination to Home.

This pattern is recommended for application-style reports.


Step 7: Apply navigation consistently across pages

To maintain a consistent experience, navigation should appear in the same location on every page.

Option 1: Copy navigation to each page

  • Select all navigation buttons

  • Group them

  • Copy and paste the group onto each page

Option 2: Use a template page

  • Create navigation on one page

  • Duplicate the page

  • Replace report visuals while keeping navigation intact


Step 8: Configure button states

Buttons support visual states that improve usability.

  1. Select a button.

  2. In the Format pane, configure:

    • Default

    • On hover

    • On press

Adjust background color, text color, or borders to indicate interactivity.


Step 9: Indicate the active page

To help users understand where they are in the report:

  • Use a distinct style for the button representing the current page

  • Apply that style only on the corresponding page

This pattern mirrors navigation behavior in Windows applications.


Step 10: Test navigation

  1. Switch to Reading view.

  2. Click each navigation button.

  3. Verify that:

    • Navigation works as expected

    • Labels match destinations

    • Layout is consistent across pages


Best practices

  • Use a Home page as the primary entry point

  • Group related pages under a single navigation area

  • Avoid overcrowding navigation with too many buttons

  • Keep navigation placement consistent

  • Use visual states to confirm user interaction