Conversation
Evonsys
US
Last activity: 12 Nov 2025 7:14 EST
Decimal property not accepting full precision when entering manual values in UI
Hi,
We have a decimal property configured with DB column type DECIMAL(18,4). When entering values through the UI, we noticed an issue with precision handling.
If we enter a value like 8888888888.75, it only accepts 888888888888.7 (one digit after the decimal) and then automatically converts it to 8888888888.70.
However, if we enter a whole number (for example, 888888888888) without decimals, it gets accepted, and the system automatically appends two decimal places (e.g., 888888888888.00).
The property uses the pxCurrency control, and the DB column mapping is correct.
Has anyone else experienced this issue or know why the UI restricts entering more than one digit after the decimal in this scenario?
Pega Infinity '23.2.3
Thanks in advance!
Pegasystems Inc.
IN
@MaleeshaW is this traditional ui or constellation? check if any edit input rules are created on property.
Evonsys
US
@Sreedhar Ganduri This is in constellation. the property does not have any edit validate or edit input rules. It is of Decimal type. And by default it is allowing 12 digits input only.
Updated: 12 Nov 2025 3:47 EST
Pegasystems Inc.
GB
@MaleeshaWI found another couple of implementations, 23.1 & 24.2.2, reporting this on My Support Portal. The default configuration in the Pega Platform sets the precision to 18 and scale to 9 for decimal fields, limiting the maximum input length to 16 characters. This was a known product defect that has been addressed in '25 (BUG-887711) and '24.2.4 (BUG-957299).
Evonsys
US
@MarcCheong Thanks for your response. Is there any workaround for this is in Pega Infinity '23.2.3?
Also, the property currently allows ONLY 12 digits, instead of 16.
There are no limitations or expected length added.
Pegasystems Inc.
GB
@MaleeshaW I'm not aware of any work around. I can't see this raised for a patch release in '23 either (earliest is 24.2.2). I would definitely raise an incident on My Pega Support, referencing this conversation. They would be able to advise best course of action - from what I can see, updating is the only way.
Evonsys
US
@MarcCheong and @Sreedhar Ganduri Thank you for your inputs on this issue.