ModelPerformanceLow
Key stored as a floating-point number
"Key stored as a floating-point number" is one of the performance checks Auditabi runs on a Power BI semantic model. n key column(s) use the double type. It is a low-severity finding: hygiene and maintainability, worth fixing when you next touch the object. Type the key as a whole number.
What is detected
n key column(s) use the double type. Keys must compare exactly: a floating-point key can fail to match its dimension row and land on the blank member.
Why it matters
Hygiene and maintainability. Fix when touching the object.
How to fix it
Type the key as a whole number.
Does your model fail this check?
Free static audit with the exact objects, no account, nothing stored.