Power BI Building Blocks
Power BI works like a small factory. Raw material enters one end, and a finished product leaves the other end. Every part has a name, a job, and a place in the chain. Knowing these names makes every later topic easier to follow.
The Bakery Analogy
Picture a neighborhood bakery. Suppliers deliver flour, sugar, and eggs. A baker follows a recipe and prepares cakes. Finished cakes sit on a display shelf, and a delivery box carries them to customers. Power BI follows the same chain with data in place of ingredients.
Bakery World Power BI World ----------------- --------------------- Suppliers ==> Data Sources Pantry and Recipe ==> Semantic Model Finished Cakes ==> Reports and Visuals Display Shelf ==> Dashboard Delivery Box ==> App
Data Source
A data source is any place that holds raw information. Excel files, CSV files, databases, websites, and cloud services all count. Power BI reads from the source and never changes the original file.
Semantic Model
A semantic model holds the cleaned tables, the relationships between them, and the calculations built on top. Microsoft used the word dataset for this part in older versions, and many tutorials still use that term. The model acts as the pantry and the recipe book together. Reports pull everything they need from it.
Report
A report is a collection of pages. Each page contains visuals, slicers, text boxes, and images. A report connects to exactly one semantic model, and anyone who opens it can click, filter, and explore the numbers.
Visual
A visual is a single chart, table, card, or map on a report page. A bar chart showing sales by city is one visual. A card showing total orders is another. Pages usually hold five to ten visuals so the story stays clear.
Dashboard
A dashboard is a single page of pinned tiles. Each tile comes from a visual in some report. Dashboards give a quick summary view, and a click on any tile opens the report behind it. Only the Power BI Service can host dashboards.
Workspace and App
A workspace is a shared folder in the cloud where a team stores reports, dashboards, and models. An app packages selected content from a workspace and delivers it to a wider audience in a tidy, read-only form.
How the Parts Connect
+-------------+ +----------------+ +----------+
| Data Source | ==> | Semantic Model | ==> | Report |
+-------------+ +----------------+ +----------+
|
v
+-----+ +-----------+ +---------+
| App | <== | Dashboard | <| Visuals |
+-----+ +-----------+ +---------+
Worked Example: A Corner Shop Owner
Meena runs a stationery shop and records daily sales in an Excel file. That file is the data source. She loads it into Power BI Desktop and adds a Products table, which creates the semantic model. She builds a report with a bar chart of sales by product and a card showing total revenue. She publishes the report to a workspace, pins her favorite visuals to a dashboard, and shares the packaged app with her two store managers.
Each step uses one building block. Meena never needs to guess which tool handles which job. The chain stays the same for every project.
Common Mix-Ups
- A report and a dashboard look similar, yet a report has many pages and a dashboard has one.
- A visual lives inside a report, while a tile lives inside a dashboard.
- A dataset and a semantic model are the same thing under two names.
Key Points
- Data sources feed a semantic model, and reports read from that model.
- Visuals are the individual charts that fill report pages.
- Dashboards pin tiles from many reports onto one page.
- Workspaces store content for a team, and apps deliver it to readers.
- The same chain applies to every Power BI project, small or large.