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 , Thank you for reaching out to the Microsoft Community Forum.
I think this is happening because Power BI is misreading the decimal separator from your Oracle data. Your view has numbers written with a comma (like 7,5), but when Power BI refreshes, it sometimes switches to using a dot decimal format (expects 7.5). When that happens, anything with a comma gets misread and turns into 0 or blank, even though the column still shows as a decimal number.
Changing the Power BI language settings doesn’t fix this issue, because those only control the user interface, not how numbers are read from data sources. You need to tell Power BI which locale to use when reading that column. In Power Query Editor, select your DESCUENTO column, go to Transform -> Data Type -> Using Locale, choose Decimal Number and then pick a locale that uses a comma as the decimal separator (for example, Spanish – Spain). Apply and close. This forces Power BI to always interpret commas correctly, regardless of your Windows or application language.
If you can edit the Oracle view, another way to fix it is to make Oracle send the number in a format with dots instead of commas. But the Power Query locale setting alone usually solves it permanently.