Calculated Columns

Calculated columns create new columns in a table using DAX.

Unlike measures, calculated columns are evaluated during data refresh and the results are stored in the Power BI model.

Calculated columns are commonly used to:

• Categorize data
• Combine values
• Create lookup values
• Build sorting columns
• Generate business attributes

What Is a Calculated Column?

A calculated column evaluates one row at a time.

General syntax:

Column Name =
Expression

Example:

Sales Amount =
FactSales[Quantity] * FactSales[Unit Price]

Power BI calculates the value for every row during model refresh.

The result is stored in the table.

Measures vs Calculated Columns

Although both use DAX, they serve different purposes.

As a general rule:

• Use measures for calculations.
• Use calculated columns to create new data attributes.

Row-by-Row Evaluation

Calculated columns automatically evaluate each row independently.

Example source data:

Calculated column:

Sales Amount =
FactSales[Quantity] * FactSales[Unit Price]

Result:

Every row receives its own calculated value.

Common Uses

Calculated columns are useful when creating:

• Product categories
• Customer segments
• Full names
• Year-Month labels
• Custom sort columns
• Status indicators

Example:

Full Name =
Customer[First Name] &
" " &
Customer[Last Name]

The new column becomes part of the data model and can be used throughout reports.

Creating Categories

One of the most common uses of calculated columns is creating business categories.

Example:

Sales Category =
IF(
    FactSales[SalesAmount] >= 1000,
    "Large Sale",
    "Standard Sale"
)

Result:

The category is stored with each row in the table.

Using SWITCH()

When multiple categories are required, SWITCH() is often easier to read than several nested IF() statements.

Example:

Performance Rating =
SWITCH(
    TRUE(),
    FactSales[SalesAmount] >= 5000, "Excellent",
    FactSales[SalesAmount] >= 2500, "Good",
    FactSales[SalesAmount] >= 1000, "Average",
    "Needs Improvement"
)

SWITCH() creates cleaner, more maintainable DAX for multiple conditions.

Combining Columns

Calculated columns can combine multiple fields into a single value.

Example:

Customer Name =
Customer[First Name]
    & " "
    & Customer[Last Name]

Result:

Using RELATED()

RELATED() retrieves a value from a related table.

Example model:

DimProduct
     |
     |
FactSales

Calculated column:

Category =
RELATED(DimProduct[Category])

The new column copies the product category from the related dimension into each sales row.

This function requires an existing relationship between the tables.

Date Calculations

Calculated columns are often used to simplify reporting dates.

Example:

Year =
YEAR(FactSales[OrderDate])

Example:

Month Name =
FORMAT(
    FactSales[OrderDate],
    "MMMM"
)

Example:

Year Month =
FORMAT(
    FactSales[OrderDate],
    "YYYY-MM"
)

These columns are useful for grouping and sorting reports.

Sorting Text Values

Power BI sorts text alphabetically by default.

Calculated columns can create a numeric sort order.

Example:

Month Number =
MONTH(DimDate[Date])

Then:

• Sort Month Name
• By Month Number

Instead of:

April
August
December
February

Power BI displays:

January
February
March
April
...
December

Practical Business Examples

Calculated columns are commonly used for:

These columns become permanent parts of the semantic model and can be reused throughout reports.

Performance Considerations

Because calculated columns are stored in the data model, they increase the model's memory usage.

Every value is calculated during refresh and saved for every row.

Example:

1 Million Rows

+ Existing Columns
+ Calculated Column

↓

1 Million Additional Stored Values

As models grow larger, unnecessary calculated columns can significantly increase refresh times and memory consumption.

Whenever possible, use measures for report calculations.

When Not to Use Calculated Columns

A common mistake is creating calculated columns for values that should be measures.

For example, avoid creating:

Total Sales =
SUM(FactSales[SalesAmount])

as a calculated column.

Why?

• It produces the same value on every row.
• It wastes storage space.
• It does not respond to report filters.
• A measure performs the calculation more efficiently.

Instead, create it as a measure:

Total Sales =
SUM(FactSales[SalesAmount])

Although the DAX looks identical, the behavior is completely different.

Choosing Between Measures and Calculated Columns

Use this guide when deciding which approach to use.

A simple rule:

If the value should change when a user filters a report, create a measure.

If the value should remain fixed for every row until the data refreshes, create a calculated column.

Best Practices

When creating calculated columns:

• Only create columns that are truly needed.
• Keep formulas simple and readable.
• Use descriptive column names.
• Avoid storing values that can be calculated dynamically.
• Use dimensions instead of duplicating descriptive data.
• Prefer measures whenever possible.

Keeping the model lean improves performance and simplifies maintenance.

Common Beginner Mistakes

Avoid these common issues:

• Creating calculated columns for totals.
• Using calculated columns instead of measures.
• Duplicating existing dimension attributes.
• Creating unnecessary text columns.
• Forgetting that calculated columns increase model size.

Many Power BI performance problems begin with overusing calculated columns.

Summary

Calculated columns are best used to create permanent attributes that become part of the data model.

They are evaluated during data refresh and stored for every row.

Measures, on the other hand, are evaluated dynamically and should be used for business calculations that respond to report filters.

Understanding the difference between these two calculation types is one of the most important Power BI skills.

Next Steps

Continue learning DAX:

• Filter Context
• Row Context
• CALCULATE
• Variables (VAR)
• Time Intelligence