Dashboards vs Reports

A Power BI report is a multi-page, fully interactive canvas built from exactly one dataset, where every visual supports cross-filtering, drill-down, and slicers. A dashboard, by contrast, is a single-page collection of tiles pinned from one or more reports — potentially spanning multiple datasets — but each tile is a static snapshot of the visual at pin time, only refreshing on a schedule rather than responding to live filter interactions.

Because dashboard tiles are pinned snapshots, clicking a tile navigates you back into the underlying report rather than filtering the dashboard itself, and tiles do not cross-filter one another even when pinned from the same report. Reports, however, support full cross-highlighting — clicking a bar in one visual filters every other visual on that page — because all visuals share the live connection to the dataset's query engine.

Dashboard tiles refresh according to the dataset's scheduled refresh (or, for real-time streaming tiles, on push), so a tile can display data that is hours old relative to the underlying source, while a report connected to the same dataset queries results at open time, subject to the same underlying dataset refresh unless it uses DirectQuery or a live connection. Tiles built from Q&A natural language queries or from Excel ranges behave similarly, snapshotting at pin time and updating only when their source dataset refreshes.

Dashboards also uniquely support data-driven alerts on numeric tiles (KPI, card, or gauge visuals), letting users set thresholds that trigger email or mobile notifications when a metric crosses a value — a capability reports do not have natively. Because dashboards render as a fixed grid of tiles, they are also the primary surface optimized for the Power BI mobile app's phone layout, whereas reports need a separate phone layout designed explicitly, or they render as a scaled-down version of the desktop layout.