This post is a part of the PL-300: Microsoft Power BI Data Analyst Exam Prep Hub; and this topic falls under these sections:
Model the data (25–30%)
   --> Design and implement a data model
      --> Identify Use Cases for Calculated Columns and Calculated Tables

Note that there are 10 practice questions (with answers and explanations) for each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available on the hub below the exam topics section.

This topic focuses on understanding when and why to use calculated columns versus calculated tables, not just how to create them. On the PL-300 exam, candidates are often tested on choosing the correct modeling approach based on performance, usability, and business requirements.

Overview: Calculated Columns vs Calculated Tables

Both calculated columns and calculated tables are created using DAX and are evaluated during data refresh, not at query time.

Understanding their appropriate use cases is critical for the exam.

Calculated Columns

What Is a Calculated Column?

A calculated column is a column added to a table using a DAX expression. The value is computed row by row and stored in the model.

Example:

Full Name = Customers[FirstName] & " " & Customers[LastName]

Common Use Cases for Calculated Columns

1. Row-Level Calculations

Use calculated columns when the result depends only on values from the current row.

Examples:

• Concatenating fields
• Categorizing values (e.g., High / Medium / Low)
• Creating flags (Yes/No)

2. Creating Columns Used for Relationships

Calculated columns are often used to:

• Create surrogate keys
• Standardize keys (e.g., trimming, formatting)
• Combine columns to form a relationship key

3. Columns Used for Slicing or Filtering

If a value is frequently used in:

• Slicers
• Page filters
• Visual-level filters

…it is often better as a calculated column than a measure.

4. Sorting Purposes

Calculated columns are required when you need to:

• Create a numeric sort column (e.g., MonthNumber)
• Use Sort by Column functionality

When NOT to Use Calculated Columns

❌ For aggregations (use measures instead)
❌ For values that must respond dynamically to slicers
❌ When logic can be handled upstream in Power Query

Calculated Tables

What Is a Calculated Table?

A calculated table is a table created using a DAX expression that returns a table.

Example:

Calendar = CALENDAR ( DATE(2020,1,1), DATE(2025,12,31) )

Common Use Cases for Calculated Tables

1. Creating Dimension Tables

Calculated tables are often used to:

• Create date tables
• Create lookup tables
• Generate disconnected tables for slicers

2. Supporting What-If or Parameter Scenarios

Calculated tables can be used for:

• What-if parameters
• Scenario selection
• Threshold or target tables

3. Creating Bridge Tables

Calculated tables are useful when:

• Resolving many-to-many relationships
• Creating intermediate tables for filtering

4. Static Aggregations

When aggregations are fixed at refresh time, a calculated table may be appropriate.

Example:

• Pre-grouped summaries
• Static reference tables

When NOT to Use Calculated Tables

❌ For data that must update dynamically with slicers
❌ When the table can be created more efficiently in Power Query
❌ For row-level calculations within an existing table

Calculated Columns vs Measures (Exam-Relevant Distinction)

This distinction is frequently tested.

If the question involves dynamic totals, measures are usually the correct answer—not calculated columns.

Performance and Model Impact

• Calculated columns and tables increase model size
• Overuse can impact refresh time
• Measures are generally more efficient for calculations that need to respond to filters

The exam often rewards candidates who:

• Minimize unnecessary calculated columns
• Prefer Power Query when possible
• Use DAX only when modeling logic is required

Common Exam Scenarios

You may be asked to:

• Choose between a calculated column and a measure
• Identify why a calculation does not respond to slicers
• Decide how to create a new table for relationships or filtering
• Optimize a model by replacing calculated columns

Common Mistakes (Often Tested)

❌ Using calculated columns for totals
❌ Expecting calculated columns to respond to slicers
❌ Creating large calculated tables unnecessarily
❌ Using DAX when Power Query is more appropriate
❌ Confusing calculated tables with measures

Best Practices for PL-300 Candidates

• Use calculated columns for row-level logic and slicing
• Use calculated tables for dimensions, bridge tables, and parameters
• Use measures for aggregations
• Prefer Power Query for data shaping
• Always consider model size and performance

Key Takeaway

Calculated columns and calculated tables are powerful modeling tools—but only when used for the right reasons.
The PL-300 exam emphasizes understanding when to use each, not just how to create them.

---

Practice Questions

Go to the Practice Exam Questions for this topic.