Many calculated columns on one table
"Many calculated columns on one table" is one of the performance checks Auditabi runs on a Power BI semantic model. n table(s) carry more than five calculated columns. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Compute them in Power Query or in the source; keep calculated columns for what genuinely needs the model.
What is detected
n table(s) carry more than five calculated columns. Each one is materialised at refresh, in the order of its dependencies, and they compress worse than columns computed upstream.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Compute them in Power Query or in the source; keep calculated columns for what genuinely needs the model.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.