Forum Discussion
PBI adding fractional decimal numbers
Microsoft Employee
Just to confirm that if the original data in SQL or other pulls (e.g. Excel below) have the fractional decimal digits? They may only show the rounded numbers to you.
If yes, you can select the column and change the number of decimal places as below.
Regards,
Thanks.
I'm a noob in PBI, so a bit struggling with some of the terminology still, but...
Therein lies the problem. It is entered/stored as "money", as in digits<decimal>2 decimal places (cents), but when it gets into the charts/graphs it starts breaking it into the finer decimals...which messes with the graphs and pop-ups. My CFO does not want to see $4,563.238999999991 when he hovers over a bar.
My guess would be, at this early stage, that when it autosums, trying to be helpful, it doesn't extract the figures into individuals again well.
Yet, as I was trying to say (without writing a book), if I export the data from the directly from the chart to a CSV, I get the original data...with just 2 cents.
The problem appears to be specifically in the charts themselves...overthinking their display plan.
Bob
hohlickContinued Contributor
Hi WTNetAdmin
As v-sihou-msft mentioned above, these could be solved by added fata format with "Modelling" tab above, where you can set 2 digits after delimeter format. I think that problem itself lies in Double-precision floating-point format
Thanks.
Yeah, I get that and understand. I'm a noob at PBI, but an old IT guy. That is a problem that we've been dealing with for a lot of years. However, that is primarily a processor problem, not a software problem.
So, a number like 4395.2300000000000000000000000000000000000 (I didn't count the decimal places) shouldn't be getting rounded up or down or dropping precision. That problem applies to something like 4395.2345876132456698732475632234 (again, arbitrary and didn't count the decimal places), as in an engineering or astronomical calc.
Summing $4395.23, and then splitting it out again should be extremely clean...in our modern software world.
I should have added...if I have to apply formatting, with this situation, I end up with rounding errors of + or - a penny in the individual row items, becuase of the fractional artifacts.