Forum Discussion
Floating point precision problem on cards
Hi dlopesc04
To avoid adding ROUND() to every measure, you can try these options:
- Change the column's data type to Fixed Decimal Number in Power Query. This ensures precision is handled at the source, so measures display clean values (like 0) without individual adjustments. Reload your model after making this change.
- Create a base measure with ROUND and reference it in other calculations. This reduces the number of edits, though it requires updating existing measures to use it.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Thanks.
Hi dlopesc04
Possibly because precision loss or imprecision occurs. - https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-data-types?utm_source=chatgpt.com#accuracy-of-number-type-calculations
I would just instead round the number to about 10 decimal values.
Yeah, it most definitely is because of that. Also adding ROUND() to the measures rounds them to 0.
But that would be beyond impractical, and would introduce another layer of 'dumb design' proofing. Do I really now have to add a ROUND() to EVERY. SINGLE. MEASURE. I. EVER. CREATE ??
Sorry, but I refuse.
Hi dlopesc04
To avoid adding ROUND() to every measure, you can try these options:
- Change the column's data type to Fixed Decimal Number in Power Query. This ensures precision is handled at the source, so measures display clean values (like 0) without individual adjustments. Reload your model after making this change.
- Create a base measure with ROUND and reference it in other calculations. This reduces the number of edits, though it requires updating existing measures to use it.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Thanks.
Hi dlopesc04
Thank you for reaching out to the Microsoft Fabric Forum Community.
I hope the information provided was helpful. If you still have questions, please don't hesitate to reach out to the community.