Why data modeling connects related tables in Power BI - Why Use It

Introduction

Data modeling in Power BI links tables that share common information. This connection helps combine data from different tables to create meaningful reports and insights without repeating data.

When you have sales data in one table and customer details in another, and you want to analyze sales by customer region.

When product information is stored separately from sales transactions, and you want to see total sales per product category.

When you want to filter data in one table based on selections made in another table, like filtering orders by date.

When you need to create reports that summarize data from multiple tables without merging them into one big table.

When you want to avoid data duplication and keep your data organized and efficient.

Steps

Step 1: Open your Power BI Desktop file

- Power BI Desktop main window

Your data tables are loaded and visible in the Fields pane

Step 2: Click the Model view icon

- Left vertical pane (Model icon)

You see all your tables as boxes with columns listed

Step 3: Drag a column from one table to the matching column in another table

- Model view canvas

A relationship line appears connecting the two tables

Step 4: Select the relationship line

- Model view canvas

Relationship settings pane opens on the right

Step 5: Check and adjust the relationship type and cardinality

- Relationship settings pane

Relationship is correctly set as one-to-many or many-to-one, ensuring accurate data connection

💡 Use one-to-many when one table has unique values and the other has repeated values

Step 6: Close the settings pane and return to Report view

- Top left corner, click Report icon

You can now create visuals that use data from both connected tables

Before vs After

Before

Tables are separate with no connections; creating a report combining customer names and sales amounts shows incorrect or incomplete data

After

Tables are connected by customer ID; reports correctly show sales amounts linked to each customer name

Settings Reference

Cardinality

📍 Relationship settings pane in Model view

Defines how rows in one table relate to rows in another table

Default: One to many

Cross filter direction

📍 Relationship settings pane in Model view

Controls how filters flow between related tables

Default: Single

Make this relationship active

📍 Relationship settings pane in Model view

Determines if the relationship is used by default in calculations

Default: Checked

Common Mistakes

Connecting tables using columns that do not have matching or unique values

This causes incorrect relationships and wrong report results

Always connect tables using columns with matching data and unique values on one side

Setting cross filter direction to Both without understanding its impact

It can cause ambiguous relationships and slow report performance

Use Single direction unless you need filters to flow both ways

Summary

Data modeling connects tables to combine related information for accurate reports.

Relationships use matching columns to link tables without merging data.

Correct relationship settings ensure data filters and calculations work properly.

Practice

1. Why do we connect related tables in Power BI data modeling?

easy

A. To make tables look colorful in the model view

B. To combine related data for accurate analysis and reporting

C. To delete duplicate rows automatically

D. To speed up Power BI software installation

Solution

1. Step 1: Understand the purpose of connecting tables

   Connecting tables links related data so you can analyze combined information easily.

2. Step 2: Recognize the benefit in reports

   Proper connections ensure reports show accurate results by relating data correctly.

3. Final Answer:

   To combine related data for accurate analysis and reporting -> Option B

4. Quick Check:

   Connecting tables = accurate combined data [OK]

Hint: Think: Why join data? To analyze together [OK]

Common Mistakes:

• Confusing visual formatting with data relationships
• Assuming connections delete duplicates
• Believing connections affect software speed

2. Which of the following is the correct way to create a relationship between two tables in Power BI?

easy

A. Use the Format pane to link tables by color

B. Write a DAX formula to join tables in the Report view

C. Drag a key column from one table to the matching column in another table in Model view

D. Copy and paste data from one table into another

Solution

1. Step 1: Identify how relationships are created in Power BI

   Relationships are made by dragging matching key columns between tables in Model view.

2. Step 2: Eliminate incorrect methods

   DAX formulas do calculations but do not create relationships; formatting and copy-paste do not link tables.

3. Final Answer:

   Drag a key column from one table to the matching column in another table in Model view -> Option C

4. Quick Check:

   Drag key columns = create relationship [OK]

Hint: Drag keys in Model view to connect tables [OK]

Common Mistakes:

• Trying to create relationships using DAX formulas
• Confusing formatting with data linking
• Copy-pasting data instead of linking

3. Given two tables: Sales with columns OrderID, ProductID, and Amount, and Products with columns ProductID and ProductName. If you create a relationship on ProductID between these tables, what will happen when you create a report showing ProductName and total Amount?

medium

A. The report will show total sales amount grouped by product name

B. The report will show blank values for product names

C. The report will show total amount without grouping

D. The report will cause an error and not display

Solution

1. Step 1: Understand the relationship effect

   Connecting on ProductID links sales to product details, enabling grouping by product name.

2. Step 2: Predict report output

   Using ProductName and total Amount will group sales amounts by each product correctly.

3. Final Answer:

   The report will show total sales amount grouped by product name -> Option A

4. Quick Check:

   Relationship on ProductID = grouped sales by product [OK]

Hint: Relationship keys enable grouping related data [OK]

Common Mistakes:

• Expecting blank product names without relationship
• Thinking totals show without grouping
• Assuming report errors without relationship

4. You created a relationship between two tables on the CustomerID column, but your report shows incorrect totals. What is the most likely issue?

medium

A. The CustomerID columns have mismatched data types or missing values

B. You forgot to format the report colors

C. The tables are too large to connect

D. Power BI does not support relationships on ID columns

Solution

1. Step 1: Check relationship keys

   For relationships to work, key columns must have matching data types and no missing values.

2. Step 2: Identify cause of incorrect totals

   If data types differ or values are missing, relationships break, causing wrong report results.

3. Final Answer:

   The CustomerID columns have mismatched data types or missing values -> Option A

4. Quick Check:

   Matching keys needed for correct totals [OK]

Hint: Check key columns data type and completeness [OK]

Common Mistakes:

• Blaming report colors for data errors
• Assuming table size prevents relationships
• Thinking Power BI disallows ID relationships

5. You have three tables: Orders, Customers, and Regions. Orders links to Customers by CustomerID, and Customers links to Regions by RegionID. You want to create a report showing total sales by region. What is the best data modeling approach?

hard

A. Create a relationship only between Orders and Regions directly

B. Join all tables into one big table before importing to Power BI

C. Use DAX to manually merge tables in the report

D. Create relationships from Orders to Customers on CustomerID, and Customers to Regions on RegionID, then use RegionName in the report

Solution

1. Step 1: Understand table connections

   Orders relate to Customers by CustomerID; Customers relate to Regions by RegionID, forming a chain.

2. Step 2: Model relationships properly

   Create relationships along this chain so data flows correctly from Orders to Regions.

3. Step 3: Use RegionName in report

   With relationships, you can group total sales by RegionName accurately.

4. Final Answer:

   Create relationships from Orders to Customers on CustomerID, and Customers to Regions on RegionID, then use RegionName in the report -> Option D

5. Quick Check:

   Chain relationships enable accurate regional sales [OK]

Hint: Connect tables stepwise using keys for multi-table reports [OK]

Common Mistakes:

• Trying to flatten tables before import unnecessarily
• Skipping intermediate relationships
• Using DAX merges instead of model relationships