Power BI dashboard examples
These Power BI dashboard examples are three report pages on example data. A regional manager sees their own sales and their real share of the company, a reader drills from a category's returns to the products behind them, and a KPI card judges orders against a target phased by last year's pattern.
Row-level security, example
One report page: £700,000 for the director, £184,200 for the North manager
- Viewed as: North regional manager. Share of company sales
- 100.0%
- The same cell, with the measure's company total read from a summary table the role doesn't filter:
- 26.3%
Viewed as: Sales director
Role: All regions (no filter)
Sales by region, October 2026
Sales
£700,000
Target
£700,000
Attainment
100.0%
| Region | Sales | Target | Attainment | Share of company sales |
|---|---|---|---|---|
| North | £184,200 | £176,000 | 104.7% | 26.3% |
| Midlands | £151,300 | £160,000 | 94.6% | 21.6% |
| South East | £238,500 | £230,000 | 103.7% | 34.1% |
| South West | £126,000 | £134,000 | 94.0% | 18.0% |
| Total | £700,000 | £700,000 | 100.0% | 100.0% |
Viewed as: North regional manager
Role: Regional manager. Share measure written over the sales table.
Role filter on Region: [Manager email] = USERPRINCIPALNAME()Sales by region, October 2026
Sales
£184,200
Target
£176,000
Attainment
104.7%
| Region | Sales | Target | Attainment | Share of company sales |
|---|---|---|---|---|
| North | £184,200 | £176,000 | 104.7% | 100.0% |
| Total | £184,200 | £176,000 | 104.7% | 100.0% |
The same cell, with the measure's company total read from a summary table the role doesn't filter: 26.3%
Show the numbers
| Region | Sales | Target | Attainment | Share of company sales |
|---|---|---|---|---|
| North | £184,200 | £176,000 | 104.7% | 26.3% |
| Midlands | £151,300 | £160,000 | 94.6% | 21.6% |
| South East | £238,500 | £230,000 | 103.7% | 34.1% |
| South West | £126,000 | £134,000 | 94.0% | 18.0% |
| Total | £700,000 | £700,000 | 100.0% | 100.0% |
Two more Power BI dashboard examples
A drillthrough from category to product
Drillthrough, example
One duvet is 21.0% of bedding sold and 60.0% of bedding returns
Returns rate by category, October 2026
Units returned ÷ units sold
Category detail
| Product | Units sold | Units returned | Returns rate | Share of category returns |
|---|---|---|---|---|
| Duvet, 13.5 tog, double | 420 | 84 | 20.0% | 60.0% |
| Pillow pair | 610 | 21 | 3.4% | 15.0% |
| Fitted sheet, king | 380 | 14 | 3.7% | 10.0% |
| Mattress topper, double | 300 | 14 | 4.7% | 10.0% |
| Duvet cover set, double | 290 | 7 | 2.4% | 5.0% |
| Bedding total | 2,000 | 140 | 7.0% | 100.0% |
Show the numbers
| Category | Units sold | Units returned | Returns rate |
|---|---|---|---|
| Bedding | 2,000 | 140 | 7.0% |
| Rugs | 800 | 33 | 4.1% |
| Towels | 2,500 | 80 | 3.2% |
| Curtains | 1,500 | 39 | 2.6% |
A reader who right-clicks Bedding lands on a page already filtered to bedding, and Power BI adds a back button. Both pages count returns against the month the order was placed, so the five products add up to the bar the reader clicked.
A Power BI KPI dashboard with a phased target
Power BI KPI dashboard, example
Orders are 2.5% behind an even target and 4.2% ahead of the seasonal one
Orders year to date, even target
97,500
Orders year to date, seasonal target
97,500
Annual target 120,000 orders. Even: 10 of 12 months = 100,000. Seasonal: last year's January to October share, 78.0% = 93,600.
The KPIs behind these Power BI dashboard examples
These are the seven measures on the three pages, grouped by page, with each formula in words ready to turn into DAX.
| KPI | Formula | A good reading | The common mistake |
|---|---|---|---|
| Sales by region | |||
| Target attainment by region | Region sales ÷ region target × 100, for the month |
The total row equals total sales ÷ total target, whoever is viewing | Storing the target as a column on the sales table. It then adds up once per order line, so keep targets in their own table at region and month grain. |
| Share of company sales | Region sales ÷ sales across all regions × 100 |
The regions add up to 100% on the director's view, and a manager sees their region's real share | Writing it over the region table and expecting it to hold for a manager. A DAX expression can't override row-level security, so the company total has to come from a table the role doesn't filter, such as a summary table. |
| Returns | |||
| Returns rate, units | Units returned ÷ units sold, for orders placed in the month |
Steady per category, with any category that jumps opened on the drillthrough page | Building the drillthrough page on the return date while the summary page uses the order date. The category then shows one rate and its products add up to another. |
| Share of category returns | Product units returned ÷ category units returned × 100 |
Close to the product's share of category units sold, or with a reason written beside it | Reading it alone. A best seller returns the most units at an ordinary rate, so set it next to the product's share of units sold. |
| Orders against target | |||
| Orders year to date | Orders placed from the first day of the financial year to the last complete day |
Moving in step with the phased target | Counting today's orders so far against a target that includes all of today. The card then reads behind every morning. |
| Phased target to date | Annual target × (last year's orders in the same months ÷ last year's full-year orders) |
Agreed with whoever set the annual target, before the year starts | Phasing evenly, as annual target ÷ 12 × months gone. A business that peaks in December then reads behind all autumn. |
| Distance to goal | (Orders to date − phased target to date) ÷ phased target to date × 100 |
At or above zero, or with an agreed plan for the gap | Handing the KPI visual the annual target. Distance to goal then shows a large shortfall until the last day of the year. |
How to build these Power BI examples
Data sources
Order lines from the order system, the targets file by region and month, a region table holding each manager's sign-in email, and a returns table where each returned line carries the order line it came from.
Grain
Sales at one row per order line. Targets at one row per region per month. Returns at one row per returned line, dated by the order it came from, so the drillthrough page and the summary page count the same month.
Refresh cadence
Sales and returns overnight. Targets only when finance issues a new version, with the version's name shown on the KPI page.
Who sees which rows
Each role filters the Region table, and the filter reaches sales and targets through their relationships. Microsoft notes it is often more efficient to put these filters on dimension tables, and they travel only through active relationships. Roles apply to people with Viewer permission in the workspace. A regional manager added as a Member sees every region, so check workspace access before blaming the role, then try each role with Test as role.
The model's shape
Sales, targets and returns are three fact tables. Region, Product and Date sit on the one side of one-to-many relationships that filter in one direction. Attainment works because Region and Date filter both sales and targets, and the two fact tables never join each other. Microsoft's guidance is to keep two-way relationships to a minimum, because they can slow queries and give report users confusing results.
Questions these dashboards should answer
The pipeline KPIs behind a regional sales page are on the sales dashboard page, and the monthly board pack, on the same kind of model, is the finance dashboard example.
These examples in other tools
Power BI
Roles are written in Power BI Desktop, and people are added to them in the Power BI service. Test as role then opens the report as that role sees it. If your team will keep the roles up after handover, our Power BI training on your own model covers writing one and testing it.
Data Studio (formerly Looker Studio)
Before rebuilding the regional page in Data Studio, decide how each manager will be kept to their own region, and test it by opening the report as a manager. Share of company sales still needs its company total from a source the manager's restriction doesn't reach, as in Power BI.
Excel
A workbook carries whatever rows were put in it. If the regional page goes out as Excel, build one file per region from the model, holding that region's rows and the company total as a single figure.
Google Sheets
The phasing in the KPI example works well in a sheet, with one row per month and last year's orders beside the target, so whoever sets the target can check the sum. Power BI Desktop can connect to Google Sheets, so the model reads that sheet as its targets table.
North's share reads 26.3% or 100.0% depending on one measure, so Power BI consultant work on your own model, part of our dashboards and reporting service, starts with a review of its relationships and measures. We test every role before you sign the pages off.
Questions about row-level security and targets
Can you build a Power BI sales dashboard with row-level security?
Yes. Each manager's role filters the region table by their sign-in email, so one report serves every region. A DAX expression can't override row-level security, so a region-against-company measure takes its total from a table the role doesn't filter, such as a summary or aggregation table. Before sharing, Test as role opens the report as each role sees it.
What makes a good Power BI KPI dashboard?
Each KPI needs a value, a target and a written reason for the target's size. Power BI's KPI visual takes a target and shows the distance to it, so the target you hand it decides whether the card reads behind. Phase an annual target by last year's monthly pattern, and say on the page which phasing it uses.
When should a report use drillthrough?
Use it when a summary page raises a question one level down, such as which product drives a category's returns. A right-click on the bar opens a detail page filtered to that value, with a back button. Build the detail page on the same date field as the summary, or its products won't add up to the bar.
Why does a total change when someone else opens the report?
If the model has row-level security, each viewer's role removes rows before any measure runs, so a total covers only what that person may see. Check workspace roles too, because row-level security applies to Viewers, and anyone added as Admin, Member or Contributor sees every row.
Can these be added to our existing Power BI model?
Yes, if region, product and date are dimension tables with one-way relationships to the facts. The roles, the drillthrough page and the phased target then go on top of what you have. If targets are a column on the sales table, or relationships filter both ways, the model needs fixing first.
Different totals for different viewers?
On the call we open the report that gives two people two totals under each role and show you whether a role filter or a measure makes the gap.