Report, Data and Model Views
Learn how to use the main views in Power BI Desktop to design reports, inspect loaded data, and manage relationships between tables. Understand how each view contributes to building reliable and meaningful business reports.
1. Introduction to Power BI Views
Power BI Desktop provides different views for working with reports and data. Each view has a specific purpose. Understanding these views helps you work efficiently and choose the correct workspace for each task.
Report View is used to design report pages, Table View is used to inspect loaded data, and Model View is used to understand relationships between tables.
Beginner Example
Samadhan is preparing a monthly sales report. He needs to create a sales chart, inspect the imported transaction records, and connect the Sales table to the Products table.
He uses Report View to create the chart, Table View to inspect the sales records, and Model View to check the relationship between the two tables.
2. Overview of the Three Main Views
The following illustration summarizes the purpose of Report View, Table View, and Model View in Power BI Desktop.
Visual 1: The purpose of the three main Power BI Desktop views.
3. Report View
Report View is the primary workspace for creating report pages. It allows you to display business information using visual elements such as charts, tables, cards, maps, and slicers.
Common Tasks in Report View
- Create charts to compare sales, products, and regions.
- Add cards to display important values.
- Insert slicers to filter report data.
- Arrange and resize visuals on report pages.
- Format titles, labels, backgrounds, and visual elements.
- Test whether visuals respond correctly to filters.
Example: Sales Performance Report
Pradnya wants to prepare a report showing total sales, monthly sales trends, and sales by product. She can use cards for totals, a line chart for monthly trends, and a bar chart for product comparisons.
Steps to Create a Visual
- Open Power BI Desktop and load a dataset.
- Select Report View.
- Choose an appropriate visual type.
- Add the required fields to the visual.
- Format the visual and arrange it on the page.
- Verify that the visual displays the expected result.
4. Table View
Table View allows you to inspect the rows and columns of tables loaded into the Power BI data model. It helps you review values, check column names, and verify that data has loaded as expected.
Example: Sales Data Table
| OrderID | Product | Region | Quantity | Sales |
|---|---|---|---|---|
| 1001 | Laptop | North | 2 | 90000 |
| 1002 | Monitor | South | 3 | 45000 |
| 1003 | Keyboard | West | 5 | 10000 |
In this example, each row represents a sales record. The columns describe the order, product, region, quantity, and sales amount.
What Can You Inspect?
- Column names and data types.
- Loaded rows and data values.
- Unexpected blank or missing values.
- Results after data preparation.
- Calculated columns and their values.
5. Understanding Table Data
Before creating a report, review the data to confirm that the expected columns and values are available. This helps identify problems before they affect report calculations.
Visual 2: Inspect table values and investigate unexpected data.
6. Model View
Model View displays the tables in the data model and the relationships between them. Relationships allow Power BI to connect related records and apply filters across tables.
Important Relationship Concepts
| Concept | Description | Example |
|---|---|---|
| One-to-many (1:*) | One record on one side can relate to multiple records on the other side. | One product can appear in many sales transactions. |
| Key column | A column used to identify or match related records. | ProductID in the Products and Sales tables. |
| Active relationship | The relationship used by default for relevant filtering and calculations. | An active relationship between Products and Sales. |
| Filter direction | Defines how filters propagate between related tables. | A product selection filters the related sales records. |
Example: Products and Sales
The Products table contains ProductID, ProductName, and Category. The Sales table contains OrderID, ProductID, Quantity, and SalesAmount.
Connecting the tables through ProductID allows a report to summarize sales by product or category without storing all product details in every sales record.
7. Example of a Data Model
A common reporting model contains a central transaction table and related dimension tables. This design is often called a star schema when dimension tables connect to a central fact table.
Visual 3: A simplified star-schema-style data model.
Steps to Inspect Relationships
- Open Model View in Power BI Desktop.
- Locate the relevant tables.
- Inspect the relationship lines between tables.
- Check the columns used for each relationship.
- Verify relationship cardinality and filter direction.
- Test the model using appropriate report visuals.
8. Comparing the Three Views
Use the task you want to complete to decide which view to open. The following table provides a quick reference.
| Task | Recommended View | Purpose |
|---|---|---|
| Create a bar chart | Report View | Create and format report visuals. |
| Display total sales in a card | Report View | Present a key business measure. |
| Inspect loaded rows | Table View | Review table data and values. |
| Review a calculated column | Table View | Inspect the calculated results. |
| Connect Products and Sales | Model View | Manage table relationships. |
| Check relationship cardinality | Model View | Understand how records relate. |
9. Choosing the Correct View
The following decision guide can help beginners select the correct view for a task.
Visual 4: A quick guide for selecting the appropriate view.
10. Practical Exercise
Samiksha has imported a dataset containing Products, Customers, and Sales tables. Complete the following tasks using Power BI Desktop.
Exercise Checklist
- Open Report View and create a chart showing sales by product.
- Add a card displaying total sales.
- Open Table View and inspect the Sales table.
- Check the column names and data types.
- Open Model View and inspect the Products-to-Sales relationship.
- Verify the relationship key and cardinality.
- Save the report as
SalesPractice.pbix.
Practice Questions
- Which view is used to design report pages?
- Which view allows you to inspect loaded rows and columns?
- Which view is used to inspect table relationships?
- Why are relationships important in a data model?
- What should you check before creating a one-to-many relationship?
- Which view would you use to create a sales chart?
- Why should you verify data values before publishing a report?
Show Suggested Answers
- Report View.
- Table View.
- Model View.
- Relationships connect related tables and support filtering and analysis.
- Check that the key on the one-side contains unique values and that the columns have compatible data types.
- Report View.
- To identify data issues and confirm that the report displays reliable results.
11. Common Beginner Mistakes
Mistake 1: Using the Wrong View
Solution: Use Report View for report design, Table View for inspecting data, and Model View for examining relationships.
Mistake 2: Ignoring Data Quality
Solution: Review unexpected values, missing data, column types, and source records before trusting the report.
Mistake 3: Creating Incorrect Relationships
Solution: Check matching columns, key uniqueness, and relationship cardinality.
Mistake 4: Choosing Visuals Without a Purpose
Solution: Select visuals that answer a specific business question.
Mistake 5: Skipping Validation
Solution: Compare report totals with trusted source data and test filters before sharing.
Summary
In this lesson, you learned how the three main Power BI Desktop views support different tasks. Report View is used to design reports, Table View is used to inspect loaded data, and Model View is used to understand relationships between tables.
Choosing the correct view helps you organize your data, identify potential problems, create meaningful visuals, and build reliable reports.