Measures vs Calculated Columns vs Power Query in Power BI (and When to Use Each)

When people first start learning Power BI, one question appears almost immediately:

Should this be a measure… a calculated column… or done in Power Query?

All three can create new values from your data.

All three can look similar at first.

But they behave very differently.

Understanding when to use each is essential if you want to build efficient Power BI models and reliable reports.

In this guide, we’ll break down what each one does, when to use them, and how to avoid the most common mistakes.

What About Power Query?

Before we compare measures and calculated columns, there’s another option to understand.

You can also create calculated columns in Power Query, before the data even reaches your model.

This is often where confusion begins.

Because technically… all three can “create new values”.

But they happen at completely different stages:

• Power Query → during data load
• Calculated columns → inside the data model
• Measures → when the report is used

In simple terms:

• Power Query = data preparation
• Calculated columns = data modelling
• Measures = reporting and analysis

What Is a Calculated Column (DAX)?

A calculated column creates a new column inside a table in your data model.

The formula is evaluated once for every row in the table.

For example:

Profit = Sales[Revenue] - Sales[Cost]

This calculation runs for each row in the dataset and the result is stored in the model.

Because the result becomes part of the dataset, calculated columns behave like any other column in your table.

You can:

• Use them in slicers
• Group by them
• Filter visuals using them
• Build relationships with them

Calculated columns create new data inside your model.

What Is a Measure (DAX)?

A measure performs a calculation dynamically when your report is viewed.

Instead of calculating a value for every row, the measure is evaluated based on the filters currently applied to the report.

For example:

Total Sales = SUM(Sales[Amount])

This measure recalculates automatically when filters change.

If a report is filtered by:

• region
• product
• time period

…the measure returns a different result.

Measures power most charts, dashboards, and aggregated values in Power BI reports.

The Key Difference

The simplest way to think about it is this:

• Power Query prepares data before it enters the model
• Calculated columns create data inside the model
• Measures calculate results at report level

Calculated columns and Power Query both store results.

Measures do not - they calculate on demand.

This difference affects performance, flexibility, and how your reports behave.

A Simple Comparison

When Should You Use Power Query?

Power Query is best used for shaping and preparing your data before it reaches the model.

Common uses include:

• Cleaning and formatting data
• Splitting or merging columns
• Changing data types
• Removing errors or duplicates
• Creating simple calculated columns

As a rule of thumb:

If something can be done in Power Query, it usually should be.

This keeps your data model smaller and more efficient.

When Should You Use a Calculated Column?

Calculated columns are useful when you need to create or categorise information inside your dataset.

Common examples include:

• Creating categories (e.g. high-value vs standard sales)
• Extracting parts of a date
• Combining columns into labels
• Creating grouping fields
• Supporting relationships between tables

For example:

Sales Category =
IF(Sales[Amount] > 1000, "High Value", "Standard")

Calculated columns are best when the result should be fixed and stored with the data.

When Should You Use a Measure?

Measures are ideal for aggregated calculations that change depending on the report context.

Typical examples include:

• Total sales
• Average revenue
• Profit margins
• Year-to-date calculations
• Percentage growth

For example:

Total Profit =
SUM(Sales[Revenue]) - SUM(Sales[Cost])

When a user filters the report, this measure automatically recalculates.

Measures allow your reports to respond dynamically to user interaction.

Why Measures Are Usually Better for Reporting

In many scenarios, measures are the preferred approach.

This is because measures:

• Use less memory
• Keep the data model smaller
• Calculate results dynamically
• Respond naturally to slicers and filters

Power Query and calculated columns both increase the size of the data model because their values are stored.

Measures only calculate results when needed.

For large datasets, this difference can significantly affect report performance.

Common Mistakes Beginners Make

Many new Power BI users confuse these three approaches.

Some common pitfalls include:

• Using calculated columns instead of Power Query
  Simple transformations should usually be done before the data reaches the model.
• Creating calculated columns for totals
  Aggregations should almost always be measures.
• Using columns when results should respond to filters
  If the value should change with report filters, it should be a measure.
• Adding unnecessary columns
  Too many calculated columns increase model size and reduce performance.

A simple question can help guide your decision:

Should this calculation change when filters change?

If the answer is yes, you need a measure.

If not, decide whether it belongs in Power Query or the data model.

Why This Difference Matters

Choosing between Power Query, calculated columns, and measures affects:

• report performance
• model size
• flexibility of analysis
• ease of maintenance

This is one of the most common areas of confusion for new Power BI users - and one of the biggest factors in building efficient, scalable reports.

Learn More

If you want to build confidence working with Power BI and DAX, our Power BI DAX Calculations and Measures training explores calculated columns, measures, CALCULATE, FILTER and time intelligence in practical reporting scenarios.

The course is delivered virtually or onsite and includes six months of post-course support to help you apply what you learn in real reporting environments.

You can also explore our wider Microsoft 365 productivity training programmes, covering Excel, Power BI and workplace data analysis.

About the Author

Susan Howard

IT Training Specialist and Facilitator with deep expertise in Microsoft Office applications, Power BI, and business systems. As Technical Training Lead at Underscore, Susan delivers engaging, hands-on courses that help professionals boost productivity, improve data confidence, and master essential digital skills across Excel, PowerPoint, Outlook, and more.