Calculated Columns vs Measures

Power BI · DAX (Data Analysis Expressions)

Theory

A calculated column is computed once per row when the data is refreshed and stored in the table, just like an imported column. It uses row context, so it can read other columns of the same row: Unit Price = DIVIDE(Sales[Amount], Sales[Qty]) gives 600 for order 101. Because it is stored, it uses memory and can be placed on slicers, axes, legends and relationships.

A measure is not stored; it is calculated at query time for each cell of a visual using the current filter context, and its result is always a single value. Total Sales = SUM(Sales[Amount]) gives a different answer per region or month. Measures cannot be used as slicer values or relationship keys, but they are what you put in the Values area. A good rule: if you need to slice or group by it, use a column (ideally in Power Query); if you need to aggregate it, use a measure.

Why we use it

Choosing correctly keeps models small and correct. Overusing calculated columns bloats memory and refresh time, while trying to slice by a measure simply does not work.

When to use it

Use a calculated column for row-level attributes needed on axes, slicers or relationships, when Power Query cannot do it. Use a measure for totals, ratios, percentages and anything that must respond to filters. When in doubt, choose a measure.

How it works

  1. Need a new calculation
  2. Will you slice, group or join by it? Yes: Create a column (Power Query or DAX). No: Create a measure.
  3. Is it a ratio or total that must follow filters? Yes: Measure is required. No: Column is acceptable.
  4. Write and format the expression
  5. Use it in the right visual well

Syntax

Calculated column: Table tools → New column
  Sales[Unit Price] = DIVIDE(Sales[Amount], Sales[Qty])
Measure: Home → New measure
  Total Sales = SUM(Sales[Amount])

Example

// Calculated column (row context, stored per row)
Price Band = IF(Sales[Amount] >= 1000, "High", "Low")

// Measure (filter context, computed per visual cell)
High Value Sales = CALCULATE([Total Sales], Sales[Price Band] = "High")

// Visual: Region on rows, [High Value Sales]
//   North ₹2,700 (1,200 + 1,500) | West ₹1,600 | South blank

Key points

Power BI topics

Power BI Introduction

Getting Data

Power Query (Data Transformation)

Data Modeling

DAX (Data Analysis Expressions)

Data Visualization

Dashboards & Reports

Power BI Service

Advanced Features

Projects & Case Studies

Interview & Certification

Advanced DAX & Time Intelligence

T
Tech Town
Log InSign Up Free
Home SQL Python DSA Power BI Snowflake Databricks Spark Gen AI Practice Problems Contest Blog

Power BI Dashboards & DAX

Learn data visualization and interactive dashboards step-by-step. Click any topic in the sidebar to open it right here.

{{ sectionCount }}
Sections
{{ topicCount }}
Topics
Free
Forever
Hands-on practice Practice DAX Online 250 business scenarios on a star schema — write a measure and compare your visual with the expected one. Start practising →
Section {{ sec.num }}

{{ sec.label }}

Power BI  /  {{ current.sectionLabel }}  /  {{ current.name }}

{{ current.name }}

Theory

{{ current.def }}

Why we use it

{{ rich.why }}

When to use it

{{ rich.when }}

Diagram

{{ rich.dg.caption }}

{{ tb.title }}
{{ c.v }}
{{ rich.dg.op }}
➜
{{ rich.dg.output.title }}
{{ c.v }}
{{ nd.label }}
{{ nd.sub }}
{{ nd.label }}
{{ nd.sub }}
{{ rich.dg.left.title }}
{{ it }}
{{ rich.dg.right.title }}
{{ it }}
On screen — where to click

{{ rich.ui.title }}

{{ u.text }}
  1. {{ st.n }}{{ st.text }}
{{ rich.ui.title }}
{{ u.text }}
Flowchart — how it works
{{ nd.text }}
{{ nd.text }}
◇ {{ nd.text }}
Yes → {{ nd.yes }}
No → {{ nd.no }}
Syntax / Where to find it
{{ current.syntax }}
Example
{{ current.example }}
What You'll Learn — click to check off
  • {{ pt.mark }} {{ pt.text }}

Share this topic