question Regarding decimal field values population in Community Central forum

Regarding decimal field values population

Sirisha24 — Tue, 29 Apr 2025 12:49:26 GMT

Hi ,

I would like to know when i give decimal values in one field and there is another dependency field which populated based on first field.
For example, if i give 12 as value in first field then second value field should be * 1000 like 12000.
But when i give 1.2 it should be 1200 right but getting as 12000

can anyone please help me how we can achieve this .

Thanks,
Sirisha

Re: Regarding decimal field values population

SAI VENKATESH — Tue, 29 Apr 2025 12:55:37 GMT

Hi @Sirisha24

You need to use field type as decimal field.

Thanks and Regards

Sai Venkatesh

Re: Regarding decimal field values population

Sirisha24 — Tue, 29 Apr 2025 12:59:48 GMT

Hi Venkatesh ,
Thanks!!
Here previously used Floating point number type for that and i was not able to change the type for that field .
Is there any approach i can follow to achieve this ?

Re: Regarding decimal field values population

Ankur Bawiskar — Tue, 29 Apr 2025 13:37:50 GMT

@Sirisha24

so that field can accept integer also and decimal also?

If yes then why not make it string and then get the number from it and multiply with the 2nd value?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Re: Regarding decimal field values population

Sirisha24 — Tue, 29 Apr 2025 13:41:46 GMT

Hi Ankur,
Thanks !!
Could you please let me know what exactly i need to do I didn't get what you have said sorry

Re: Regarding decimal field values population

Robert H — Tue, 29 Apr 2025 14:08:33 GMT

Hello @Sirisha24

Can you please share the script that you are using to do the calculation?

In Javascript, the result should always be 1200, no matter if 1.2 is a string or an actual decimal number.

Regards,

Robert

Re: Regarding decimal field values population

SAI VENKATESH — Tue, 29 Apr 2025 20:06:52 GMT

Hi @Sirisha24

the only point is that if we use integer type or other type ServiceNow will not allow to show the outputs in decimals . We need to use correct data type to achieve these things.

Thanks and regards

Sai venkatesh

Re: Regarding decimal field values population

Ankur Bawiskar — Wed, 30 Apr 2025 04:46:56 GMT

@Sirisha24

what's your requirement here?

As per my suggestion I informed to use string field so that user can enter either integer or decimal

If my response helped please mark it correct and close the thread so that it benefits future readers.

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 05:28:27 GMT

Hi Robert ,
We are using a system property to retrieve a value (e.g., 1000), which is then multiplied by the number of days to calculate the equivalent NFI cost. This calculation is implemented in a client script, as shown in the code snippet, which populates the u_equivalent_nfi_cost field accordingly.

Thanks ,
Sirisha

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 05:30:10 GMT

Hi Ankur ,

As you suggested i can't change type now so i need to do that scenario in different way because its all customization things.
Thanks,
Sirisha

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 05:33:28 GMT

Hi Venkatesh ,

The actual requirement is: when a value like 10 is entered in the "Number of Days" field, the "NFI Cost" field should correctly calculate the cost based on the defined conditions (e.g., 10 × 1000 = 10000). Similarly, if the input is 2.5, the cost should be calculated as 2.5 × 1000 = 2500. However, the current behavior is incorrect—when entering 2.5, it is being treated as 25, resulting in a cost of 25000. This issue needs to be fixed so that decimal values are handled properly.

Thanks,
Sirisha

Re: Regarding decimal field values population

Robert H — Wed, 30 Apr 2025 06:46:43 GMT

Hello @Sirisha24 ,

I guess you are doing the replaceAll() because some countries use the comma (,) as the decimal separator? But you are not replacing it with a dot (.) which is the expected separator in JavaScript.

Please do this instead:

var nDays = g_form.getDecimalValue('FIELD_NAME');

And ideally you should recreate that field as a Decimal type field if it is currently a String field.

Regards,

Robert

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 06:57:45 GMT

Hi Robert ,

If i gave this condition also it is going as 56 instead of 5.6.

Re: Regarding decimal field values population

Robert H — Wed, 30 Apr 2025 07:05:36 GMT

Hello @Sirisha24 ,

What is the user actually entering in the field? Is it 5,6 (comma) or 5.6 (dot)?

And what is value of the "glide.system.locale" System Property, and the "Country code" of that user in the sys_user table?

Regards,

Robert

Re: Regarding decimal field values population

Ankur Bawiskar — Wed, 30 Apr 2025 07:02:37 GMT

@Sirisha24

please share your script which you are using

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 07:57:13 GMT

Hi Robert ,
They are actually using both.
The value of 1000 in the system properties is correct.

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 07:59:19 GMT

Hi,

This is the client script where 1000 value is getting from system property .

Re: Regarding decimal field values population

Robert H — Wed, 30 Apr 2025 08:11:51 GMT

Hello @Sirisha24 ,

Then advise your users that they have to enter the numbers in the correct format, with dot (.) as the decimal separator. They cannot just choose whatever format suits them.

Since you are not using a Decimal type field for the input the system cannot help you with enforcing the correct format, and you would have to write a very complex script for guessing the actual number that was entered.

Take the number 1234.56 as an example.

In the US it would be written as "1,234.56" but in other countries that would mean "1.23456".

Other countries write it as "1234,56", but in the US it would mean "123456".

Regards,

Robert

Re: Regarding decimal field values population

Sirisha24 — Wed, 30 Apr 2025 08:18:40 GMT

Hi Robert,

In this case, decimals are not working either—for example, 2.8 is not accepted, even though you mentioned decimals should be supported.
From a user perspective, the inputs are coming from many different locations, so we need to support both comma and dot as decimal separators—for example, users might enter 2.9 or 2,9.
Is it possible to handle both formats?