Why data modeling connects related tables in Power BI - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do we connect related tables in data modeling?

In Power BI, why is it important to create relationships between related tables?

A To enable filtering and aggregation across tables for accurate reports

B To make tables load faster in Power BI Desktop

C To prevent users from editing data in the tables

D To reduce the file size of the Power BI report

💡 Hint

Think about how data from different tables can work together in reports.

Connecting related tables allows Power BI to filter and summarize data correctly across tables, enabling accurate and meaningful reports.

❓ dax_lod_result

intermediate

DAX measure with related table filter

Given two tables: Sales and Products connected by ProductID, what is the result of this DAX measure?

SalesAmountFiltered = CALCULATE(SUM(Sales[Amount]), Products[Category] = "Beverages")

If Sales table has amounts: 100, 200, 300 for products in categories Beverages, Snacks, Beverages respectively, what is the measure value?

A 600

B 400

C 300

D 100

💡 Hint

Only sum amounts where product category is Beverages.

The measure sums Sales amounts only for products in the Beverages category, which are 100 and 300, totaling 400.

❓ visualization

advanced

Choose the correct visualization for related tables

You have two related tables: Customers and Orders. You want to show total orders per customer with a clear connection between them. Which visualization best shows this?

A A line chart showing order amounts over time without customer info

B A pie chart showing total orders by order date

C A table showing customers without order totals

D A bar chart showing total orders by customer name

💡 Hint

Think about showing totals grouped by customer.

A bar chart grouped by customer name clearly shows total orders per customer, leveraging the relationship between Customers and Orders tables.

🔧 Formula Fix

advanced

Why does this report show incorrect totals?

You created a report summing sales amounts, but totals are too high. You have two tables: Sales and Customers. You forgot to create a relationship between them. What is the likely cause?

A Without a relationship, Power BI sums all sales repeatedly for each customer, inflating totals

B Power BI automatically creates relationships, so this should not happen

C The sales amounts are stored as text, causing wrong sums

D The report filter is set to exclude customers, causing totals to be low

💡 Hint

Think about how missing relationships affect data aggregation.

Without a relationship, Power BI cannot match sales to customers properly, causing duplicated sums and inflated totals.

🎯 Scenario

expert

Designing a data model for sales and products

You have two tables: Sales with columns (SaleID, ProductID, Quantity, Amount) and Products with (ProductID, ProductName, Category). You want to analyze total sales by product category. What is the best data modeling approach?

A Merge both tables into one to avoid relationships

B Create a many-to-many relationship between Sales and Products on ProductID

C Create a one-to-many relationship from Products (one) to Sales (many) on ProductID

D Create a relationship from Sales (one) to Products (many) on ProductID

💡 Hint

Think about which table has unique products and which has multiple sales per product.

Products table has unique ProductID values (one side), and Sales has many rows per product (many side). A one-to-many relationship from Products to Sales on ProductID is best.

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