Money Attribute Updates as NaN with Non-English Locales

Products

• Clarity PPM On Premise
• Clarity PPM SaaS
• Clarity FedRAMP

Issue/Introduction

In many non-English locales (such as Spanish, Italian, and French), the comma is used as the standard decimal separator instead of the period (dot).

When a user with a non-English locale attempts to update a money-type attribute in the Modern UX Details flyout or the Properties page using a dot as the decimal separator, the application fails to save the value correctly. Instead, the value is rendered as "NaN" (Not a Number).

STEPS TO REPRODUCE:

1. Navigate to Administration > Studio > Objects > Project object.
2. Create a new attribute of the Money data type.
3. Add this new field to the MUX project grid.
4. Log in as a user with a US English locale and enter the value 10.25 (using a dot separator) into the grid. Observe that it saves correctly.
5. Change the user's locale to Spanish. Enter the value 11.25 (using a dot separator) into the grid. Observe that it saves correctly.
6. Still using the Spanish locale, enter the value 12,25 (using a comma separator) into the grid. Observe that it saves correctly.
7. Open the Details flyout. Enter the value 13,25 (using a comma separator). Observe that it saves correctly.
8. In the Details flyout, enter the value 14.25 (using a dot separator).

Expected Results: The value should be processed and saved correctly, adapting to the input format.

Actual Results: The value is not saved when a dot is used as a separator in the Details flyout (or Properties page) with a non-English locale; the field displays "NaN".

Note: This behavior is consistent across both the Details flyout and the Properties page.

Environment

Clarity 16.4.0

Cause

DE182132

Resolution

Fixed in 

• Clarity 16.4.2