Calculated columns vs measures in Power BI - Quick Revision & Key Differences

Recall & Review

beginner

What is a calculated column in Power BI?

A calculated column is a new column added to a table using a formula. It is computed row by row when data is loaded or refreshed and stored in the data model.

beginner

What is a measure in Power BI?

A measure is a calculation used to aggregate data dynamically based on filters or slicers. It is computed on the fly when you interact with reports.

intermediate

When should you use a calculated column instead of a measure?

Use a calculated column when you need a value for each row that can be used in slicers, filters, or relationships. For example, categorizing data by a new label.

intermediate

How do measures improve report performance compared to calculated columns?

Measures calculate results only when needed and based on current filters, so they use less memory and can be faster than calculated columns which store data for every row.

beginner

Can a measure be used in a table visual like a calculated column?

Yes, measures can be used in table visuals but they show aggregated results based on the current filter context, not row-by-row values like calculated columns.

Which of the following is true about calculated columns?

A They are calculated once and stored in the data model.

B They calculate results dynamically based on filters.

C They cannot be used in slicers or filters.

D They only work with numeric data.

Calculated columns are computed once during data refresh and stored in the model for each row.

What is a key advantage of using measures over calculated columns?

A Measures are stored in the data model for each row.

B Measures require more memory than calculated columns.

C Measures cannot be used in visuals.

D Measures calculate results dynamically based on user interaction.

Measures calculate results on the fly depending on filters and slicers, making reports more flexible.

When would you prefer a calculated column over a measure?

A When you need a value for each row to create relationships or filters.

B When you want to aggregate data dynamically.

C When you want to reduce data model size.

D When you want to calculate totals only.

Calculated columns provide row-level values useful for filtering and relationships.

Which statement about measures is FALSE?

A Measures respond to slicers and filters.

B Measures can be used in charts and tables.

C Measures calculate values for each row individually.

D Measures are not stored in the data model as columns.

Measures calculate aggregated results, not row-by-row values.

What happens when you add a calculated column to your data model?

A It cannot be used in visuals.

B It increases the size of the data model.

C It creates a dynamic calculation based on filters.

D It reduces the data model size.

Calculated columns add data for each row, increasing the model size.

Explain the main differences between calculated columns and measures in Power BI.

Think about when calculations happen and how results are stored or displayed.

Describe a scenario where you would choose a calculated column instead of a measure.

Consider when you want to slice or filter data by a new attribute.

Practice

1. Which of the following best describes a calculated column in Power BI?

easy

A. A visual element used to display data on a report page.

B. A dynamic calculation that changes based on filters and user selections.

C. A new column added to a table with values calculated row by row and stored in the model.

D. A type of filter applied to slicers in reports.

Solution

1. Step 1: Understand what a calculated column is

   A calculated column is created by adding a new column to a table where each row's value is computed and stored permanently.

2. Step 2: Differentiate from measures

   Measures are dynamic and calculate results on the fly based on filters, unlike calculated columns which are static.

3. Final Answer:

   A new column added to a table with values calculated row by row and stored in the model. -> Option C

4. Quick Check:

   Calculated column = static row-level data [OK]

Hint: Calculated columns store data row-wise; measures calculate dynamically [OK]

Common Mistakes:

• Confusing calculated columns with measures
• Thinking calculated columns change with filters
• Believing measures create new table columns

2. Which of the following is the correct syntax to create a row-by-row calculated column in Power BI using DAX?

easy

A. NewColumn = SUM(Sales[Amount])

B. NewColumn = Sales[Quantity] * Sales[Price]

C. Measure = CALCULATE(SUM(Sales[Amount]))

D. NewColumn := Sales[Quantity] + Sales[Discount]

Solution

1. Step 1: Identify calculated column syntax

   Calculated columns use simple assignment with = and row context expressions like Sales[Quantity] * Sales[Price].

2. Step 2: Check options for correct syntax

   NewColumn = Sales[Quantity] * Sales[Price] uses correct syntax and row-level calculation. NewColumn = SUM(Sales[Amount]) uses aggregation which is for measures. Measure = CALCULATE(SUM(Sales[Amount])) defines a measure, not a column. NewColumn := Sales[Quantity] + Sales[Discount] uses := which is invalid in DAX.

3. Final Answer:

   NewColumn = Sales[Quantity] * Sales[Price] -> Option B

4. Quick Check:

   Calculated column syntax = simple row formula [OK]

Hint: Calculated columns use = with row-level expressions, not aggregation [OK]

Common Mistakes:

• Using aggregation functions in calculated columns
• Using := instead of = in DAX
• Confusing measure syntax with calculated column syntax

3. Given the following DAX measure:

Total Sales = SUM(Sales[Amount])

and a calculated column:

Discounted Price = Sales[Price] * 0.9

What will be the result of Total Sales if a report filter selects only products with Discounted Price less than 100?

medium

A. The sum of Sales[Amount] for all rows where Discounted Price is less than 100.

B. The sum of Sales[Amount] for all rows, ignoring the filter on Discounted Price.

C. An error because measures cannot use calculated columns in filters.

D. Zero, because Discounted Price is not a measure.

Solution

1. Step 1: Understand filter context on measures

   Measures calculate dynamically and respect report filters, including filters on calculated columns.

2. Step 2: Apply filter on Discounted Price

   The filter selects rows where Discounted Price < 100, so Total Sales sums only those rows' Amount values.

3. Final Answer:

   The sum of Sales[Amount] for all rows where Discounted Price is less than 100. -> Option A

4. Quick Check:

   Measures respect filters on calculated columns [OK]

Hint: Measures recalc with filters, including on calculated columns [OK]

Common Mistakes:

• Thinking measures ignore filters on calculated columns
• Believing calculated columns cannot be used in filters
• Assuming error occurs when filtering on calculated columns

4. You wrote this DAX measure:

Total Discount = SUM(Sales[Discounted Price])

but it returns an error. What is the most likely cause?

medium

A. Discounted Price is a calculated column, but the table Sales does not contain it.

B. Discounted Price is a measure, and measures cannot be summed directly.

C. Discounted Price is a calculated column, so SUM cannot be used on it.

D. Discounted Price is a calculated column but the column name is misspelled.

Solution

1. Step 1: Understand SUM usage on calculated columns

   SUM can be used on calculated columns if they exist in the table.

2. Step 2: Check for existence and spelling

   If the column does not exist or is misspelled, SUM will cause an error. The most likely cause is that the calculated column Discounted Price does not exist in the Sales table.

3. Final Answer:

   Discounted Price is a calculated column, but the table Sales does not contain it. -> Option A

4. Quick Check:

   SUM errors if column missing [OK]

Hint: Check column existence before summing [OK]

Common Mistakes:

• Assuming SUM cannot be used on calculated columns
• Confusing measures and columns in aggregation
• Ignoring spelling or table errors

5. You want to create a report showing the average sales per customer, but only for customers who bought more than 5 items. Which approach is best?

hard

A. Create a calculated column counting items per customer, then a measure averaging sales filtered by that column.

B. Create a measure summing sales and ignore item counts.

C. Create a calculated column averaging sales per customer and filter customers in the report.

D. Create a measure that calculates total items per customer and filters average sales dynamically.

Solution

1. Step 1: Understand dynamic filtering needs

   Filtering customers by items bought requires dynamic calculation because user filters may change.

2. Step 2: Choose measure for dynamic aggregation

   A measure can calculate total items per customer and filter average sales dynamically, adapting to report filters.

3. Step 3: Why not calculated columns?

   Calculated columns are static and cannot respond to slicers or filters dynamically, so Create a calculated column counting items per customer, then a measure averaging sales filtered by that column. is less flexible.

4. Final Answer:

   Create a measure that calculates total items per customer and filters average sales dynamically. -> Option D

5. Quick Check:

   Use measures for dynamic filtering and aggregation [OK]

Hint: Use measures for dynamic filters and aggregations [OK]

Common Mistakes:

• Using calculated columns for dynamic filters
• Ignoring filter context in measures
• Trying to average in calculated columns