CROSSJOIN involving a fact table
"CROSSJOIN involving a fact table" is one of the performance checks Auditabi runs on a Power BI semantic model. n expression(s) cross-join 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. Use the relationship and CALCULATE instead, or cross-join dimensions only.
What is detected
n expression(s) cross-join a fact table. The intermediate result is the product of both row counts and is materialised in memory before anything else happens.
Why it matters
Wrong in some filter contexts, slow, or fragile under change. Fix in the next iteration.
How to fix it
Use the relationship and CALCULATE instead, or cross-join dimensions only.
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