Bird
Raised Fist0
Power BIbi_tool~10 mins

Star schema concept in Power BI - Cell-by-Cell Formula Trace

Choose your learning style10 modes available
LearnWhyDeepSheetTryChallengeScenarioRecallDash
Sample Data

Sample data showing a star schema with a fact table (Orders) and two dimension tables (Customers and Products).

CellValue
A1OrderID
B1CustomerID
C1ProductID
D1OrderDate
E1Quantity
F1SalesAmount
A21001
B2C01
C2P01
D22024-01-10
E22
F240
A31002
B3C02
C3P02
D32024-01-11
E31
F325
A41003
B4C01
C4P03
D42024-01-12
E43
F475
H1CustomerID
I1CustomerName
J1Region
H2C01
I2Alice
J2North
H3C02
I3Bob
J3South
L1ProductID
M1ProductName
N1Category
L2P01
M2Pen
N2Stationery
L3P02
M3Notebook
N3Stationery
L4P03
M4Chair
N4Furniture
O1Price
O220
O325
O425
Formula Trace
SUMX(Orders, Orders[Quantity] * RELATED(Products[Price]))
Step 1: Evaluate RELATED(Products[Price]) for each row in Orders
Step 2: Calculate Quantity * Price for each row
Step 3: SUMX sums all calculated values
Cell Reference Map
Orders Table:       Products Table:
+-------+---------+   +---------+-------+
|OrderID|ProductID|   |ProductID| Price |
|  1001 |  P01    |   |   P01   |  20   |
|  1002 |  P02    |   |   P02   |  25   |
|  1003 |  P03    |   |   P03   |  25   |
+-------+---------+   +---------+-------+
   |          \___________/
   |                     
   +--------------------->
Orders table references Products table by ProductID to get Price for calculation.
Result
+-----------------+
| Total Sales = 140|
+-----------------+
The total sales amount calculated by multiplying quantity by product price and summing all orders.
Sheet Trace Quiz - 3 Questions
Test your understanding
What does the RELATED function do in the formula?
ASums all quantities in Orders
BFetches matching product price from Products table
CFilters Orders by ProductID
DCalculates total sales directly
Key Result
SUMX iterates over fact table rows, multiplying measure by related dimension value, then sums results.

Practice

(1/5)
1. What is the main characteristic of a star schema in Power BI?
easy
A. A single table with all data combined
B. Multiple fact tables connected in a chain
C. One central fact table connected to multiple dimension tables
D. Only dimension tables without any fact table

Solution

  1. Step 1: Understand star schema structure

    A star schema has one main fact table that stores measurable data.

  2. Step 2: Identify dimension tables role

    Dimension tables provide descriptive attributes and connect to the fact table.

  3. Final Answer:

    One central fact table connected to multiple dimension tables -> Option C

  4. Quick Check:

    Star schema = One fact + many dimensions [OK]
Hint: Remember star schema looks like a star with one center [OK]
Common Mistakes:
  • Thinking multiple fact tables form a star schema
  • Confusing dimension tables as fact tables
  • Assuming star schema has no fact table
2. Which of the following is the correct way to describe the relationship in a star schema?
easy
A. One-to-many from dimension tables to fact table
B. Many-to-many between fact and dimension tables
C. One-to-many from fact table to dimension tables
D. One-to-one between fact and dimension tables

Solution

  1. Step 1: Identify relationship direction

    Dimension tables filter many rows in the fact table, so one dimension row relates to many fact rows.

  2. Step 2: Confirm relationship type

    This means a one-to-many relationship from dimension to fact table.

  3. Final Answer:

    One-to-many from dimension tables to fact table -> Option A

  4. Quick Check:

    Dimension to fact = one-to-many [OK]
Hint: Dimension filters many facts, so one-to-many from dimension [OK]
Common Mistakes:
  • Reversing the relationship direction
  • Choosing many-to-many which is not typical in star schema
  • Assuming one-to-one relationships
3. Given a star schema with a Sales fact table and a Product dimension table, what happens if you slice sales by product category?
medium
A. The report shows total sales without any filtering
B. Sales values are grouped by product category from the dimension table
C. Sales values are ignored because categories are not in the fact table
D. An error occurs because dimension tables cannot filter facts

Solution

  1. Step 1: Understand slicing in star schema

    Slicing by product category uses the Product dimension to filter the Sales fact table.

  2. Step 2: Effect on sales values

    Sales are grouped and summed by the selected product categories.

  3. Final Answer:

    Sales values are grouped by product category from the dimension table -> Option B

  4. Quick Check:

    Slicing by dimension groups facts [OK]
Hint: Dimensions slice facts to group data in reports [OK]
Common Mistakes:
  • Thinking dimension filters do not affect fact data
  • Assuming error occurs when slicing by dimension
  • Believing sales values are ignored
4. You created a star schema but your report shows incorrect totals when filtering by a dimension. What is the most likely cause?
medium
A. The report uses a pie chart instead of a bar chart
B. The fact table has duplicate rows
C. The dimension table has too many columns
D. The relationship between fact and dimension tables is inactive or missing

Solution

  1. Step 1: Check relationships in star schema

    Inactive or missing relationships prevent filtering from dimension to fact table.

  2. Step 2: Impact on report totals

    Without active relationships, filters do not apply correctly, causing wrong totals.

  3. Final Answer:

    The relationship between fact and dimension tables is inactive or missing -> Option D

  4. Quick Check:

    Active relationships needed for correct filtering [OK]
Hint: Verify relationships are active to fix filtering issues [OK]
Common Mistakes:
  • Blaming duplicate rows without checking relationships
  • Thinking chart type affects data filtering
  • Ignoring relationship status
5. You want to optimize a Power BI model with sales data. Which star schema design improves query speed and report clarity?
hard
A. One large fact table with keys to small, focused dimension tables
B. Multiple fact tables with duplicated dimension data inside each
C. One fact table with all dimension attributes merged inside it
D. Only dimension tables with no fact table

Solution

  1. Step 1: Understand star schema optimization

    A large fact table with keys to small dimension tables reduces data duplication and improves performance.

  2. Step 2: Avoid poor designs

    Duplicating dimension data or merging all attributes in fact table causes slow queries and confusion.

  3. Final Answer:

    One large fact table with keys to small, focused dimension tables -> Option A

  4. Quick Check:

    Star schema = big fact + small dimensions [OK]
Hint: Keep fact big and dimensions small for best speed [OK]
Common Mistakes:
  • Duplicating dimension data in fact tables
  • Merging all data into one table
  • Removing the fact table entirely
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard