Understanding Row Context

What is Evaluation Context?

Before diving into Row Context, let's briefly define Evaluation Context. Think of it as the "environment" or "surroundings" in which a DAX formula is calculated. The context determines which data is visible to your formula, and therefore, what result it produces. Row context and its sibling, filter context, are the two components of this environment.

Part 1: Defining Row Context - The "Current Row"

The simplest way to think of Row Context is that it means "the current row." When a row context is active, DAX knows which specific row of a table it's working on, allowing it to access values from any column in that single row.

The most common place you'll see row context is in calculated columns.

As the article explained, when you write a formula for a calculated column like Sales[Quantity] * Sales[Net Price], DAX automatically creates a row context. It iterates through the Sales table, row by row, performing the multiplication for each "current row" and storing the result.

This image perfectly visualizes the process. For each row, the DAX engine can see the values in that row's Quantity and Unit Price columns to compute the Line Amount.

Part 2: Where Row Context Doesn't Exist (And Why Measures Fail)

Now, let's try to use that same logic in a measure. If you create a new measure and type the exact same formula, Sales[Quantity] * Sales[Net Price], Power BI will give you an error.

Why? Because measures, by default, do not have a row context. A measure is designed to work over a whole column or table, often aggregating thousands of rows. When you write Sales[Quantity], you're not telling DAX which row's quantity you want. Is it the first row? The last? The average? Without a "current row," the request is ambiguous and the formula fails.

To understand this critical distinction, let's continue with the SQLBI article.

This is a fundamental concept in DAX:

• A calculated column is evaluated for each row in the table. It has an innate row context.
• A measure is evaluated in the context of a visual or filter. It has no innate row context.

So, how do we perform row-by-row calculations inside a measure? We need to create a row context ourselves.

Part 3: Creating Row Context with Iterator Functions

To solve this problem, DAX provides a special class of functions called iterators. These functions are often identifiable by the "X" at the end of their name, such as SUMX, AVERAGEX, and COUNTX.

An iterator function does two things:

1. It takes a table as its first argument.
2. It then iterates through that table, row by row. For each row, it creates a temporary row context and evaluates an expression you provide.

Let's see this in action. The following video gives a fantastic visual explanation of how an iterator creates a row context within a measure.

To solidify what you just saw, let's read the final part of the SQLBI article which details the SUMX function.

So, the correct measure for Total Revenue is:
Total Revenue = SUMX(Sales, Sales[Quantity] * Sales[Net Price])

Here, SUMX iterates over the Sales table, and for each row, it multiplies Quantity by Net Price. After calculating all the individual row results, it sums them up to produce the final, correct total.

Your Turn: Experiencing Row Context

Let's apply these concepts in your Power BI file.

1. Create a Calculated Column (Implicit Row Context):

   • Navigate to the Data View in Power BI and select your Sales table.
   • Go to the Table tools ribbon and click New column.
   • In the formula bar, enter the following DAX formula and press Enter:

     Line Total = Sales[Quantity] * Sales[Unit Price]
     

   • Observe how a value is calculated for every single row. This is row context in action, provided automatically.

2. Attempt to Create a Failing Measure:

   • Go back to the Report View.
   • In your Key Measures table, right-click and select New measure.
   • Try to use the same formula as before:

     // This will produce an error
     Bad Revenue Measure = Sales[Quantity] * Sales[Unit Price]
     

   • Notice the error message. Power BI is telling you it cannot determine a single value for the columns because there is no row context.

3. Create the Correct Measure with an Iterator:

   • Now, create the correct measure using SUMX:

     Revenue (SUMX) = 
     SUMX(
         Sales,
         Sales[Quantity] * Sales[Unit Price]
     )
     

   • Create a card visual on your report canvas and add the Revenue (SUMX) measure to it. You will see it calculates the correct total revenue by performing the multiplication for each row and then summing the results.

Conclusion

Excellent work! You've just grasped one of the most challenging but essential concepts in DAX. Understanding the presence (or absence) of row context is the key to debugging your formulas and moving beyond simple aggregations.

Key Takeaways:

• Row Context means "the current row" and allows DAX to see values in the columns of that specific row.
• Row context is automatically created in calculated columns.
• Measures do not have a default row context, which is why referring directly to a column in a measure causes an error.
• Iterator functions (like SUMX) are used to manually create a row context inside a measure, enabling row-by-row calculations.

Preview of the Next Lesson:
Now that you understand row context, we're ready to explore its sibling: Filter Context. Filter context is created by your report visuals, slicers, and other DAX functions. In the next lesson, we will define filter context and see how it works together with row context to enable truly dynamic and powerful analysis.