Guides

DAX Row Context vs Filter Context in Power BI

By Ravindra Bagale, Power BI & Data Analytics trainer · LinkedIn · Published: 30 September 2026 · Last updated: 30 September 2026

Filter context is the set of filters from slicers, visuals and the Filters pane that decide which rows a measure sees; row context is the “current row” while a calculated column or an iterator (like SUMX) evaluates — two contexts, two jobs.

Filter context → which rows a measure sees
Row context    → which row an expression is on

Why two contexts, rows in / number out

Same three rows:

Filter context demo

1. Card with [Total Sales] = SUM ( Sales[Amount] ).
2. No slicer → rows in: all three. Number out: 220.
3. City slicer = Mumbai → rows in: A and B. Number out: 140.
4. That “which rows are visible” world is filter context.

Row context demo

1. New column: TaxCol = Sales[Amount] * 0.18.
2. On row A, Amount is 100, so TaxCol is 18.
3. On row B, Amount is 40, so TaxCol is 7.2.
4. The formula knows this row’s Amount without SUM. That is row context.

Why both exist:

1. Managers ask for totals that react to slicers → measures + filter context.
2. Each slip needs its own tax stamp → columns + row context.
3. Mixing the two without language is why students say “DAX is random.”

What do I need before this guide?

• A simple [Total Sales] measure (DAX beginner).
• Optional: SUM vs SUMX.
• Course: Evaluation context.

Before and after (look at the tables first)

Filter context = which rows a measure sees (Mumbai → 150). Row context = “this row” inside iterators like SUMX. Different tools, different jobs.

Part A — Feel filter context

1. Card with [Total Sales].
2. City slicer → Mumbai.
3. Number drops to 140.
4. Matrix with City on rows — each cell is a different filter context.

Part B — Feel row context

1. New column: TaxCol = Sales[Amount] * 0.18.
2. Browse Data view — each row has its own tax.
3. Slicers do not rewrite that stamped column the way a measure recalculates.

Part C — Iterators bring row context into measures

Line Total =
SUMX (
    Sales,
    Sales[Qty] * Sales[UnitPrice]
)

Vertical reading:

1. SUMX walks Sales rows (row context each time).
2. Multiplies Qty × UnitPrice on that row.
3. Adds the results — under the outer filter context of the visual.
4. City = Mumbai still limits which rows enter the loop.

FreshBasket story (fictional)

1. TaxCol stamps every order slip with 18% tax (row).
2. [Total Sales] adds Amount only for slips still on the desk after the City slicer (filter).
3. Phone-bill analogy: the line items on your bill are row context; “total due this month” after you filter one month is filter context.

Mistakes and calm fixes

Ghabru naka 😅 — naming the context is half the battle.