Forum Discussion
AdministratorNumber interpretation error after updating tables in PowerBi
Hi Syndicate_Admin , Thank you for reaching out to the Microsoft Community Forum.
I don’t think this isn’t a Power Query conversion problem at all. The decimals are already gone before Power BI even starts applying your steps. In the Source preview your values are integers, which means Power BI is receiving the data from Oracle after something upstream has already stripped or rounded the decimals. Once that happens at the source, no locale setting in Power Query can recover them.
When you connect to Oracle, open the Advanced options -> SQL statement box and write a query that forces Oracle to send the discount as text with a known decimal separator. Then in Power Query, convert that text to a decimal using Change Type -> Using Locale. This bypasses the driver and locale issues that are dropping the decimals and it guarantees that Power BI receives the exact numeric format you want on every refresh.
Community SupportHi Syndicate_Admin , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
AdministratorHello again
I have applied step by step what you indicate. I show what I have done.
I have gone to Power Query, I have right-clicked on the DISCOUNT column and I have chosen the option "Change type" and after that, I have indicated "Use locale".
Next, I have selected the options that were recommended to me:
I hit the "OK" button. And then the "Apply and Close" button. Then I have "Applied the changes".
Next, I have checked in "Transform data" if these have been modified correctly.
To my surprise, although I have applied all the proposed measures, the data are still not transformed. The numbers are integers and keep being replaced in the wrong way.
Thanks for the help.
- v-hashadapu
Hi Syndicate_Admin , Thank you for reaching out to the Microsoft Community Forum.
I don’t think this isn’t a Power Query conversion problem at all. The decimals are already gone before Power BI even starts applying your steps. In the Source preview your values are integers, which means Power BI is receiving the data from Oracle after something upstream has already stripped or rounded the decimals. Once that happens at the source, no locale setting in Power Query can recover them.
When you connect to Oracle, open the Advanced options -> SQL statement box and write a query that forces Oracle to send the discount as text with a known decimal separator. Then in Power Query, convert that text to a decimal using Change Type -> Using Locale. This bypasses the driver and locale issues that are dropping the decimals and it guarantees that Power BI receives the exact numeric format you want on every refresh.