Issue Summary
When saving an attribute value using comma as the decimal separator, the separator is removed, leading to a wrong value. The problem is inverted (dot is removed) when using locales that default to comma (such as Dutch or German).
Steps to Reproduce
Modality 1 - English locale
- Create an object type with a float attribute.
- Give it any value with a dot decimal separator, such as 1.5.
- In the list view, edit the value to use a comma as the decimal separator, such as 1,5.
- The separator is removed and the value is saved as 15.
Modality 2 - German locale
- Create an object type with a float attribute.
- Give it any value with a comma decimal separator, such as 1,5.
- In the list view, edit the value to use a dot as the decimal separator, such as 1.5.
- The separator is removed and the value is saved as 15.
(In the object edit view, the issue was not reproducible. In this case, the separator is replaced by a dot or comma, depending on the locale, but the value is not modified).
Expected Results
Assets should fully respect the usage of the default decimal separator, as some locale settings use commas instead of dots (for example, Dutch and German). Editing of float attributes should be saved correctly, and the values should also be consistently displayed depending on the locale.
In previous versions, the error message "Number is not valid (Float)" would be displayed. Apparently, the "fix" on bug JSDSERVER-15703 resulted in this new behaviour.
Actual Results
The value is modified, as the separator is lost.
Workaround
Use a dot or comma as a decimal separator, depending on the case.
Versions Tested
| Testing Requirements |
Version |
Affected Version |
| Customers Reported Version |
10.3.5 |
Yes |
| Most Recent Bug-Fix Release |
10.5.0 |
Yes |
| Previous Major Release |
10.3.3 |
No |
| Most Recent LTS |
10.3.5 |
Yes |
| Previous Supported LTS |
10.3.3 |
No |
Bug
Medium
