What Is the Difference Between a Calculated Column and a Measure?
In Power BI, a calculated column and a measure are both ways to add a calculation to a model with DAX, but they behave very differently. A calculated column is computed row by row when the data is loaded and stored as a new column in the table. A measure is computed on the fly at query time, in the context of whatever a visual is showing, and stores no values. The short version: a calculated column is a value sitting in a row, while a measure is a calculation that runs when you look at it. Choosing the right one is one of the most common points of confusion for people learning DAX.
How a Calculated Column Works
A calculated column is evaluated once per row when the model refreshes, using values from that same row, and the result is stored in the table just like an imported column. Because the values are precomputed and saved, a calculated column takes up memory and can be used anywhere a normal column can: on an axis, as a slicer, or as a filter. A typical use is deriving a category from existing fields, such as a price band or a full name built from first and last name. The cost is that the values are fixed at refresh time and consume model memory.
How a Measure Works
A measure is evaluated at query time, not at refresh, and only for the specific slice of data a visual is asking for. It responds to filter context: the same measure for total sales returns the company total on one visual and a single region’s total on another, because it recalculates for whatever filters apply. Measures store no data, so they add almost nothing to model size, and they are the right tool for aggregations such as sums, averages, ratios, and time calculations. The trade-off is that a measure produces a single aggregated result for its context, so it cannot sit on a row or be used directly as a slicer.
When to Use Each
Use a calculated column when you need a per-row value that you will group by, slice on, or filter with, and when the value does not depend on what a visual is showing. Use a measure for anything that aggregates or that should react to filters: totals, percentages, running totals, year-over-year comparisons. A useful default is to prefer a measure whenever you can, because measures are lighter on memory and respond to context, and to reach for a calculated column only when you genuinely need a stored, per-row value. Putting an aggregation in a calculated column when it should be a measure is one of the most common modeling mistakes.
Calculations on a Governed Data Foundation
Whether a calculation belongs in a column or a measure is easier to get right when the underlying model is well structured and the core business logic is already defined once, in a shared place. When every author writes their own measures against raw ERP tables, the same metric ends up calculated several slightly different ways. QuickLaunch builds governed data foundations for JD Edwards, Vista, NetSuite, and OneStream with pre-built semantic models that ship core measures already defined, so teams extend a consistent set of enterprise Power BI data models rather than rebuilding the basics report by report.
Frequently Asked Questions
What Is the Difference Between a Calculated Column and a Measure?
A calculated column is computed row by row at refresh and stored in the table, so it can be used on an axis, slicer, or filter. A measure is computed at query time for the current filter context and stores no values, which makes it the right choice for aggregations like sums, ratios, and time calculations.
Should I Use a Calculated Column or a Measure?
Prefer a measure whenever you can, because measures are lighter on memory and respond to filters. Use a calculated column only when you need a stored, per-row value to group by, slice on, or filter with, and the value does not depend on what a visual is showing.
Do Measures and Calculated Columns Use the Same Language?
Yes. Both are written in DAX. The difference is not the language but when and how they are evaluated: a calculated column once per row at refresh, a measure at query time within the current filter context.
