Power QueryPerformanceLow
Grouping applied after a merge
"Grouping applied after a merge" is one of the performance checks Auditabi runs on a Power BI semantic model. n query(ies) group rows after a merge. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Aggregate before merging, or do both in the source.
What is detected
n query(ies) group rows after a merge. The merge materialises both tables, then the group re-reads everything: the two heaviest operations run back to back in the mashup engine.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Aggregate before merging, or do both in the source.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.