Ratio computed row by row inside an iterator
"Ratio computed row by row inside an iterator" is one of the reliability checks Auditabi runs on a Power BI semantic model. n measure(s) divide inside SUMX or AVERAGEX. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Compute the two totals first and divide once, unless the per-row ratio really is the intent.
What is detected
n measure(s) divide inside SUMX or AVERAGEX. The result is the sum or the average of per-row ratios, which is almost never the ratio of the totals shown in the visual.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Compute the two totals first and divide once, unless the per-row ratio really is the intent.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.
More DAX checks
- Arithmetic or comparison on a measure that returns text
- Measure returning text in one branch and a number in another
- Share denominator clears a fact-table column instead of the dimension
- "Previous period" window overlaps the current one
- Percentage label built without ×100
- Percentages and amounts summed together