Our Example: Sales Table
We're using the Sales table so you can see how the same four rows behave completely differently once context transition enters the picture.
OrderID | Product | Region | Quantity | Unit Price |
1 | Laptop | North | 2 | ₹50,000 |
2 | Mouse | South | 5 | ₹800 |
3 | Laptop | South | 1 | ₹50,000 |
4 | Keyboard | North | 3 | ₹1,500 |
Part 1: What Is Context Transition?
DAX Context Transition is what happens the moment CALCULATE (or CALCULATETABLE) is evaluated while row context is still active for example, inside a calculated column. CALCULATE takes every column value from the current row and converts it into an equivalent filter, as if you had manually filtered the table down to just that row. This is the exact mechanism that lets a calculated column "reach into" an aggregation and get a row-aware answer, instead of the flat, whole-table answer a plain SUM would give.
Without Context Transition
When used directly in a calculated column, SUM does not automatically convert the current row context into filter context. It therefore evaluates the column over the table rather than restricting the aggregation to the current row.
OrderID | Product | Quantity | Product Total (Naive) |
1 | Laptop | 2 | 11 |
2 | Mouse | 5 | 11 |
3 | Laptop | 1 | 11 |
4 | Keyboard | 3 | 11 |
Every row shows the same value 11 the grand total quantity across all four rows. Row context existed, but SUM never consulted it.
Part 2: Real Example Turning Row Context Into Filter Context
Now wrap the same measure in CALCULATE, and narrow it back down with ALLEXCEPT so it only respects the Product column:
Here's the sequence DAX actually runs, on every row: CALCULATE sees it's sitting inside row context, so it performs context transition first freezing every column value on that row (OrderID, Product, Region, Quantity, Unit Price) into an implicit filter. ALLEXCEPT then strips that filter back down to just Product, leaving a proper filter context of "every row that shares this row's product." Only then does SUM run.
OrderID | Product | Quantity | Total by Product |
1 | Laptop | 2 | 3 |
2 | Mouse | 5 | 5 |
3 | Laptop | 1 | 3 |
4 | Keyboard | 3 | 3 |
Now the two Laptop rows both show 3 (2 + 1), Mouse shows 5, and Keyboard shows 3 each row is aware of its siblings. That awareness is only possible because context transition handed the calculation off from row context into filter context.
What Just Happened, in Plain Terms
- CALCULATE noticed it was running inside row context one row, evaluated in isolation, just like Post 15 described.
- Before SUM ever ran, CALCULATE performed context transition: it converted every column value on that row into an equivalent filter.
- ALLEXCEPT then peeled that automatic filter back down to only the Product column.
- The result: a calculated column that behaves as if it can see its sibling rows something plain row context alone can never do.
Row Context vs Filter Context vs Context Transition
Row Context | Filter Context | Context Transition | |
Created by | Calculated columns, iterators (SUMX, FILTER, RANKX…) | Report visuals, slicers, CALCULATE, relationships | CALCULATE / CALCULATETABLE evaluated inside row context |
Scope of awareness | One single row at a time | A filtered subset of rows across the model | Converts one row's values into a filter, then hands off |
Analogy | A cursor moving down an Excel row | A WHERE clause wrapped around your table | The moment the cursor's row gets frozen into a WHERE clause |
Frequently Asked Questions
Does context transition happen automatically?
Yes. CALCULATE and CALCULATETABLE perform context transition when they are evaluated while row context is active. Also remember that when a measure is referenced inside an iterator, Power BI implicitly applies CALCULATE to the measure, so context transition can occur automatically.
Is context transition the same thing as using CALCULATE?
Not quite. CALCULATE evaluates an expression in a modified filter context. When it is evaluated while row context is active, it also performs context transition by converting the current row context into filter context.
Why does my calculated column with CALCULATE return one value per row instead of a total?
Because context transition converts every column in that row into a filter, which usually narrows the filtered set down to exactly one row the row itself.