Power QueryPerformanceLow
Rows filtered after the join is expanded
"Rows filtered after the join is expanded" is one of the performance checks Auditabi runs on a Power BI semantic model. n query(ies) filter rows after expanding a joined table. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Filter before joining, so the join works on the rows you keep.
What is detected
n query(ies) filter rows after expanding a joined table. The join runs on the full set and the filter throws most of it away afterwards.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Filter before joining, so the join works on the rows you keep.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.