Problem with decimal field behavior when using commas as decimalsDescriptionWhen commas are used as decimals in fields, they may be moved, causing incorrect input after saving the record unless the correct country_code is configured. Symptoms Using a comma (,) for the decimal instead of a period (.) results in incorrect input to a decimal type field. If for example, you enter 10,10 into the field (in this case, it represents 10.10 Kilograms in Brazil): After you leave the field, and it validates with the server, the server thinks that the comma is used as a delimiter for thousands on an integer and marks it 1,010: CauseThis issue is caused by not having the correct country_code configured in the user's record in sys_userResolutionMake sure that the language is set to English to make this change or you may not know which field you are looking for.Login as admin or maint and navigate to sys_users.LIST.Find the record of the user that is having the issue.Change the value of the field country_code to the country that customer lives in. It is more than likely set to System by default.Save the changes and verify.Additional InformationCreate a country code product documentation