Guides

How to Build Your First Power BI Dashboard

By Ravindra Bagale, Power BI & Data Analytics trainer · LinkedIn · Published: 30 September 2026 · Last updated: 30 September 2026

A Power BI dashboard is a one-screen canvas of pinned tiles in the Power BI Service. You design interactive report pages in Desktop, Publish, then pin visuals to assemble the dashboard managers actually open every morning.

Report (Desktop) → Publish → Pin tiles → Dashboard (Service)

What do I need before this guide?

• A report with at least two visuals (first report).
• A Microsoft account that can publish to a workspace you are allowed to use.
• Product map: Desktop vs Service vs Mobile.
• Course: Report vs dashboard.

Before and after (look at the tables first)

Build a report, publish, pin a visual. A dashboard tile can show a filtered total — Online channel → 140.

Why report first, dashboard second

What a report is

A report is one or more pages of interactive visuals you build in Desktop (and view in the Service). Slicers, drill and cross-highlight live here.

What a dashboard is

A dashboard is a Service canvas of pinned tiles. Usually one monitoring screen. Clicking a tile often jumps you back into the report for detail.

Why you care

1. People say “dashboard” for every chart page — interviews expect Microsoft’s meanings.
2. Managers want a morning glance board, not ten exploratory pages.
3. If you only share a report, that can be enough. Dashboards shine for curated at-a-glance views.

Tiny numbers for the layout:

1. Total Sales Card → 140 (Mumbai 100 + Pune 40).
2. Orders Card → 2.
3. Trend and a small City table underneath.

Part 1 — Design the report page properly

What this step is: building clean visuals that are worth pinning.

Why you care: a messy page becomes a messy dashboard.

Vertical layout recipe:

1. Top row: 3 Card visuals — Total Sales (140), Orders, Average Amount (measures).
2. Middle: one line or column chart for trend by Date or Month.
3. Bottom: a table of City / Category / Amount (Mumbai 100, Pune 40).
4. Add one City slicer — not five noisy slicers.
5. Titles in plain English: “Sales by month”, not “Chart 1”.
6. Align edges; leave breathing room; avoid rainbow themes on day one.

Why this layout pins well

1. Cards become small KPI tiles.
2. The trend becomes a wide tile.
3. The table becomes a detail tile managers click into.

What you see on screen in Desktop: three cards on top, one chart, one table, one slicer.

Part 2 — Publish from Desktop

What this step is: sending your .pbix into a Service workspace.

Why you care: dashboards do not live in Desktop — pins happen in the cloud.

Vertical steps:

1. Sign in to Desktop with the account that has rights.
2. Home → Publish.
3. Choose the target workspace (My workspace is fine for learning).
4. Wait for success; follow the link to open in the Service if offered.
5. Confirm the dataset and report both appear in the workspace.

What you see on screen: a success message and a workspace list with your report name.

Publish gotchas

1. Wrong account → workspace list looks empty or forbidden.
2. Huge files need patience on first upload.
3. After Publish, further Desktop edits need Publish again (or use deployment habits later).

Part 3 — Pin tiles to a dashboard

What this step is: copying a live snapshot of a visual onto a dashboard canvas.

Why you care: this is the moment a “report page” becomes a Service dashboard.

Vertical steps:

1. In the Service, open the published report.
2. Hover a Card → pin icon.
3. Choose New dashboard, name it FreshBasket Morning.
4. Pin the trend chart and the table the same way (existing dashboard).
5. Open the dashboard from the workspace navigation.
6. Drag corners to resize; drag tiles to rearrange.

What you see on screen: tiles showing 140, the chart, and the City table; you can drag them like fridge magnets.

Pinning tips

1. Pin the final formatted visual — formatting travels with what you pinned (with some Service nuances over time).
2. If you change the report heavily, you may re-pin or use dashboard tile refresh behaviours — verify after edits.
3. Do not pin twenty tiles on day one; six is plenty.

Part 4 — Make it “manager friendly”

Vertical checklist:

1. KPI names sound like business, not table names (Total Sales, not Sum of Amount).
2. Trend answers “are we up or down?”
3. Detail table answers “where?” (Mumbai vs Pune).
4. Optional: set a data alert on a KPI tile if your licence supports it (Service feature).
5. Optional: open Mobile layout tools so phones are not a mess.
6. Document the refresh schedule so the board is not yesterday’s story forever.

Part 5 — Share without chaos

1. Prefer workspace roles / apps for teams (course Service chapter).
2. Avoid mailing .pbix as your only “share” strategy.
3. Check that the audience is allowed to see the underlying dataset.
4. Remember: sharing is a governance topic — fictional FreshBasket training data is safe; real HR data is not a casual pin party.

Report vs dashboard — interview table

Common mistakes

Tile hygiene checklist

1. No overlapping tiles.
2. KPI tiles same height.
3. One clear title on the dashboard.
4. Remove unused sample dashboards from learning workspaces so demos stay clean.
5. After changing a measure name, verify tiles still make sense.

From dashboard back to report

1. Click a tile.
2. Land in the report visual context.
3. Use slicers for deep dive (Mumbai → sales 100).
4. Return to dashboard for the executive glance.

That round-trip is the product design — teach it in demos.