Iterates over each table row, evaluating an expression, then totals those results; text, logical values and blanks don't count.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains SUMX in context, with comparison tables and the common traps.
Terms in this definition
- OVER
Gives a T-SQL window function its window: PARTITION BY, ORDER BY and, if wanted, a ROWS or RANGE frame. Rankings and running totals can then be worked out while every row is kept.
- Event
Table in Log Analytics where entries from Windows event logs are kept.
- Logical
Independent of any implementation. Each logical design is made real through a physical counterpart.
- VALUES
Returns in DAX the distinct column values, or table rows, still visible after filters are applied, sometimes with an extra blank entry. CALCULATE often takes the result as a table filter.
- COUNT
A DAX function returning how many non-blank numbers, dates or text values a column contains. Boolean columns need COUNTA instead, and for counting the rows of a table COUNTROWS is the better choice.
Related terms
- Iterator
A DAX function like SUMX that steps through a table one row at a time, evaluating an expression in row context, and then aggregates what it gets.
- Row context
Exists automatically in calculated columns and inside iterators like SUMX, giving DAX a current row to work on. Filtering the model is left to filter context; a current row does not do that by itself.
- SUM
Totals every numeric value held in one column. Where each row needs its own expression evaluated first, SUMX is needed.