Building your first Power BI dashboard is more approachable than it looks. The free Power BI Desktop app does the heavy lifting, and the flow is always the same: load your data, model it lightly, drop in a handful of well-chosen visuals, add slicers, theme it, and save. This guide walks you through that exact flow with a simple sales example, so you finish with a real report instead of a blank canvas.
What You Need Before You Start
You only need two things: the app and some data.
- Power BI Desktop — free from Microsoft. Download it from the Microsoft Store or microsoft.com. It runs on Windows only. (If you're on a Mac, you'll need a Windows VM or a cloud desktop.)
- A data file — a clean CSV or Excel file works perfectly for a first dashboard. The cleaner the source, the less work later.
A few quick definitions so the rest of this makes sense:
- Power BI Desktop is the free authoring tool where you build reports.
- The Power BI Service is the web app (app.powerbi.com) where you publish and share. Sharing typically requires a paid Power BI Pro license — roughly $14 per user per month as of 2026, though check Microsoft's pricing page for current rates.
- A .pbix file is your saved report. (You may also see .pbip — Power BI Project format — which saves the same content as readable folders for version control. Stick with .pbix for now.)
- A semantic model (formerly called a "dataset") is the tables, relationships, and measures behind your visuals.
For this walkthrough, imagine a Sales.csv with columns like OrderID, OrderDate, Region, Category, Product, Quantity, and Revenue.
Step 1: Get Your Data In
Open Power BI Desktop, and on the Home ribbon click Get data. Pick Text/CSV (or Excel workbook), choose your file, and you'll see a preview window.
Click Transform Data rather than Load — this opens the Power Query Editor, where you clean data before it reaches your report. Even for a first dashboard, do a couple of basic checks:
- Confirm column data types. Dates should be a date type,
Revenuea decimal number,Quantitya whole number. A wrong type here breaks math and time charts later. The type icon sits on the left of each column header. - Remove obvious junk. Delete blank columns or summary rows that snuck in from Excel.
- Trim and clean text if your
RegionorCategoryvalues have stray spaces (select the column, right-click, then Transform).
When it looks right, click Close & Apply. Power Query records every step as a repeatable recipe, so when you refresh with next month's file, the same cleanup runs automatically.
Step 2: Model Lightly
For one flat table you can skip ahead, but most real reports benefit from a date table, which unlocks proper time intelligence (month-over-month, year-to-date, and so on).
The fastest way is a calculated table. On the Modeling tab choose New table and paste:
Calendar =
ADDCOLUMNS (
CALENDAR ( DATE ( 2023, 1, 1 ), DATE ( 2026, 12, 31 ) ),
"Year", YEAR ( [Date] ),
"Month", FORMAT ( [Date], "MMM" ),
"MonthNumber", MONTH ( [Date] ),
"YearMonth", FORMAT ( [Date], "YYYY-MM" )
)
Then create a relationship: switch to the Model view (the diagram icon on the left) and drag Sales[OrderDate] onto Calendar[Date]. This is the core idea of a star schema — a central fact table (Sales) connected to descriptive dimension tables (Calendar, and later Region or Product lookups). Keeping that shape clean is the single biggest thing that makes Power BI behave.
While you're here, sort your month names correctly: select the Month column, then on the Column tools tab use Sort by column and choose MonthNumber. Otherwise charts list April before January.
Add one or two measures
Measures are reusable calculations that respond to filters. Don't overdo it — two or three is plenty for a first build. Right-click your Sales table, choose New measure, and add:
Total Revenue = SUM ( Sales[Revenue] )
Total Orders = DISTINCTCOUNT ( Sales[OrderID] )
Measures are smarter than dragging a raw column onto a card, because they recalculate correctly for whatever slicer or filter context the visual sits in.
Step 3: Add the Core Visuals
Switch to Report view. You build by clicking a visual type in the Visualizations pane, then dragging fields into its wells. A solid starter dashboard has four pieces.
| Visual | What it shows | Fields to use |
|---|---|---|
| Card | Headline numbers | Total Revenue, Total Orders |
| Line chart | Trend over time | Axis: Calendar[YearMonth], Values: Total Revenue |
| Bar chart | Comparison by category | Axis: Category, Values: Total Revenue |
| Table or matrix | The detail behind the visuals | Product, Quantity, Total Revenue |
A practical order to build them:
- Cards first. Drop two Card visuals at the top for
Total RevenueandTotal Orders. These answer "how are we doing?" at a glance. - Trend line. Add a Line chart with months on the axis and revenue as the value. This is where the date table pays off — the line reads left to right in calendar order.
- Category bar. Add a Clustered bar chart (or column) with
Categoryand revenue. Sort it descending by value so the biggest contributor sits on top — click the visual's...menu and choose Sort axis. - Detail table. Add a Table visual with a few columns. This gives people the underlying numbers without exporting.
Arrange them in a grid: cards across the top, the line chart and bar chart in the middle, and the table along the bottom. Leave breathing room — crowded reports are hard to read.
Step 4: Add Slicers So People Can Explore
A slicer is an on-canvas filter. Click an empty area, choose the Slicer visual, and drag a field into it. Good starter slicers:
Calendar[Year]— as buttons or a dropdownRegion— as a dropdown to keep it compact
By default, every visual on the page filters together, so picking "West" in a Region slicer updates the cards, both charts, and the table at once. You can also click a single bar to cross-filter the rest of the page — that interactivity is free, and it's what makes a dashboard feel alive versus a static screenshot. If you want a visual to ignore a slicer, use Format → Edit interactions.
Step 5: Theme It So It Looks Finished
Default Power BI colors are fine, but a consistent theme is what separates a draft from something you'd send to a manager.
- On the View ribbon, open the Themes gallery and pick one, or import a custom JSON theme to match your brand colors, fonts, and backgrounds in one shot.
- Set readable titles on every visual (Format pane → General → Title).
- Format your numbers — currency on revenue, no stray decimals on counts. Do this on the measure (Measure tools → Format) so it applies everywhere at once.
- Add a simple text box title at the top so the page names itself.
If you'd rather not hand-write theme JSON, our free Power BI theme generator builds a valid theme file you can import directly. A consistent palette across cards and charts does more for perceived quality than any single fancy visual.
Step 6: Save, and Optionally Publish
Save with File → Save as to create your .pbix. That file holds the report, the model, and (for an imported CSV) a snapshot of the data.
To share, click Publish to send it to a workspace in the Power BI Service, where colleagues can view it in a browser — note that viewing and sharing generally require Pro licenses. If you just need to hand someone the report, sending the .pbix is fine; they open it in free Power BI Desktop.
A Realistic First-Build Checklist
[ ] Data loaded via Get data → Transform Data
[ ] Column types confirmed in Power Query
[ ] Date table created and related to the fact table
[ ] 2-3 measures written (SUM, DISTINCTCOUNT)
[ ] 2 KPI cards
[ ] 1 trend line chart (by month)
[ ] 1 category bar chart (sorted descending)
[ ] 1 detail table
[ ] 2 slicers (date + one dimension)
[ ] Theme applied + number formats set
[ ] Saved as .pbix
Work top to bottom and you'll have a clean, interactive report rather than a pile of disconnected charts. Once this flow feels natural, the next steps are richer modeling and time-intelligence DAX — covered in our DAX basics guide and data modeling guide.
Don't want to wrangle Power Query, relationships, and DAX on your first try? Send Instant PowerBI your CSV or Excel file and get back a finished, branded, fully-modeled report — KPI cards, trends, slicers, and a clean theme — as a file that opens right in the free Power BI Desktop. Get started and skip straight to the insights.
Frequently asked questions
Is Power BI free to build a dashboard?
Yes. Power BI Desktop, the app you use to build reports, is free on Windows. You only need a paid license (Power BI Pro, roughly $14 per user per month as of 2026) to publish and share reports through the Power BI Service web app. Building and saving a .pbix file locally costs nothing. Check Microsoft's pricing page for current rates.
What data do I need to build a Power BI dashboard?
A clean CSV or Excel file is enough for a first dashboard. Ideally it has one row per record (such as one row per order) with clearly typed columns: a date, one or more categories, and a numeric value to measure. The cleaner the source, the less cleanup you'll do in Power Query.
What visuals should a beginner dashboard include?
Start with four: KPI cards for your headline numbers, a line chart for the trend over time, a bar chart to compare categories, and a table for the underlying detail. Add one or two slicers (such as date and region) so viewers can filter everything on the page at once.
What is the difference between a .pbix and a semantic model?
A .pbix is the saved report file you create in Power BI Desktop, containing visuals, the data model, and imported data. A semantic model (formerly called a dataset) is the layer inside it: your tables, relationships, and DAX measures. The report's charts sit on top of the semantic model.
Build Power BI reports for a living? Do this part in minutes.
Studio turns a data export and a sentence into a valid .pbip project — TMDL model, PBIR report pages, DAX measures, branded theme. You keep the judgment calls; the clicking is done.
See Studio →