Issue Summary
The decimal separator behaviour is inconsistent and does not follow the locale standards. For example, when an instance is configured to run in a DE locale, number formatting standards should default to a comma instead of a dot. Exporting data from Assets should also retain the standard, but this is not what is observed.
Steps to Reproduce
- Set up a JSM environment running the German or any other locale that uses a comma instead of a dot as a decimal separator.
- Create a new object schema and a few objects containing an attribute of value type "float" ("Gleitkomma").
- Create new objects and modify the value of the float attribute using a comma. Observe that when saving the value, it shows a comma in the Assets view.
- Open the same object in the detailed view by clicking its key. Observe that the value shows a dot instead of a comma. Editing the value with a comma or a dot makes no difference.
- Now, return to the Assets view and export all objects to CSV. Observe that in the resulting file, the format retains the dot standard, not the comma.
Expected Results
Assets should fully comply with the locale options by using the chosen (comma) decimal separator.
Actual Results
The behaviour is inconsistent.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available.
Versions Tested
| Testing Requirements |
Version |
Affected Version |
| Customers Reported Version |
10.3.7 |
Yes |
| Most Recent Bug-Fix Release |
| Previous Major Release |
10.7.0 |
Yes |
| Most Recent LTS |
|
|
| Previous Supported LTS |
|
|
Bug
Low
