Power BI

Report vs. Dashboard (Power BI)

Also called: Power BI dashboard, Power BI report, Pinned tiles

In Power BI, a report is a multi-page, interactive view of one semantic model. A dashboard is a single page of tiles pinned from one or more reports in the Power BI service.

A multi-page Power BI report with a Region slicer, cards, a column chart and page tabs. Two of its visuals are pinned as tiles onto a single-page dashboard that also holds tiles from a finance report and an operations report.

The short version

In everyday speech, “dashboard” means any page of charts. In Power BI, it’s a specific object, and most of what people call a “Power BI dashboard” is actually a report.

ReportDashboard
PagesOne or manyExactly one
Where it’s builtPower BI Desktop or the servicePower BI service only
DataOne semantic modelTiles from one or more reports
InteractivitySlicers, cross-filtering, drill-downClick a tile to open its source report
FiltersSlicers and the filter paneNone on the dashboard itself

How pinning works

A dashboard doesn’t have its own visuals. You open a published report in the Power BI service, hover over a visual, and pin it to a new or existing dashboard. The tile keeps the filters and slicer selections that were active when you pinned it.

In the example, the Revenue YTD card and the Revenue by region chart are pinned from a sales report. The same dashboard also holds a Gross margin tile from a finance report and a Late deliveries tile from an operations report. That ability to combine sources on one screen is the main reason to build a dashboard.

You can also pin a whole report page as a live tile, which keeps the page interactive inside the dashboard.

When to use each

Use a report for almost everything: exploring data, answering questions, and giving people pages they can filter. Reports are where the design work goes, from layout to KPI cards and slicers.

Add a dashboard when:

  • Leaders want one screen across several reports, such as sales, finance and operations together.
  • You want data alerts on a few key numbers. Dashboard tiles showing a card, KPI or gauge can notify owners when a threshold is crossed.
  • People need a landing page that points into the detailed reports.

If none of those apply, skip the dashboard. A well-designed first report page usually does the same job with less to maintain.

Common mistakes

  • Designing the dashboard first. Dashboards are assembled from report visuals, so the report layout is what needs designing.
  • Expecting slicers to carry over. A pinned tile won’t respond to a slicer on the report. It shows whatever was selected at pin time.
  • Rebuilding the report as a dashboard. A dashboard of twenty tiles from one report adds a click and a maintenance job, and nothing else.

Mocking up a Power BI report

Since the report is where the real layout lives, that’s what to mock up: pages, visuals and slicers. Our guide to mocking up a Power BI dashboard before you build it walks through it.

Related terms

Common questions

Can you create a dashboard in Power BI Desktop?
No. Dashboards are a Power BI service feature. You build the report in Power BI Desktop (or the service), publish it, and then pin visuals from the published report to a dashboard in the service.
Can a Power BI dashboard have slicers?
Not directly. Dashboard tiles have no slicers or filter pane of their own, and a pinned visual keeps the filters that were applied when it was pinned. To give viewers filters, send them to the report, or pin a whole report page as a live tile.
Should I build a report or a dashboard?
Build the report first, since dashboards are made from reports. Add a dashboard only if people need one screen that brings together numbers from several reports, or want data alerts on key tiles. Many teams never need one.

Mock it up before you build it

Lay out your Power BI or Tableau dashboard in Mockko, get sign-off, then build. Free to start.

Try Mockko free