Calculated columns on a fact table
"Calculated columns on a fact table" is one of the performance checks Auditabi runs on a Power BI semantic model. n calculated column(s) live on a fact table. It is a medium-severity finding: the model still works, but results are wrong in some filter contexts, slow, or fragile under change. Create them in Power Query (or the source) so they compress like any other column, unless they depend on other model tables.
What is detected
n calculated column(s) live on a fact table. They are computed at refresh, stored uncompressed relative to source columns, and cannot fold to the source.
Why it matters
Severity depends on how many objects are affected.
How to fix it
Create them in Power Query (or the source) so they compress like any other column, unless they depend on other model tables.
Reference
Microsoft: Power BI modeling guidance — calculated columns
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