Regarding decimal field values population
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 05:49 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2025 12:01 AM - edited 04-30-2025 12:05 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2025 12:57 AM
Hi Robert ,
They are actually using both.
The value of 1000 in the system properties is correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2025 01:11 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2025 01:18 AM
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?