

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
click for more info
Not enough gems
Cost: 6 gems
1: DAX
incomplete
2: Logical Functions – IF
incomplete
3: SWITCH Function
incomplete
4: Time Intelligence Functions
incomplete
5: More Time Functions
incomplete
6: Add Columns
incomplete
7: Aggregations
incomplete
8: Aggregations As Measures
incomplete
9: Iterators
incomplete
10: Calculated Columns vs. Measures
incomplete
11: Context in DAX
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
A common mistake in DAX is using aggregators like SUM in calculated columns instead of measures. Don't do that! It will return the same number on every row because calculated columns are row-by-row, not a single value for the whole table.
This means:
It doesn't respond to filters.
It takes up storage in your model.
It behaves incorrectly in visuals.
A SUM in a calculated column is almost never what you want.
Instead, use a measure for aggregations! A measure is a single value that recalculates dynamically based on the current filter context. This means it:
Changes when you slice by date, customer, or product
Returns different values depending on the visual
Uses no extra storage
Reflects how much was sold in the filtered context
Measures think in totals; columns think row-by-row. An aggregator like SUM belongs in a measure.