Columns removed after merges or expansions
"Columns removed after merges or expansions" is one of the performance checks Auditabi runs on a Power BI semantic model. n query(ies) merge/expand first and remove columns at the end. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Select the needed columns (Table.SelectColumns) as early as possible, before merges.
What is detected
n query(ies) merge/expand first and remove columns at the end. Intermediate steps carry every column, which costs memory and time on large sources.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Select the needed columns (Table.SelectColumns) as early as possible, before merges.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.