Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error message on English instead of Russian



Project has a section with a few properties on it that have validation. It includes a standard validation for Integer, since the property is of an Integer type too.

For wrong value entered the custom validation message is being displayed.

But if user somehow refreshes this section, for example, by changing value of property that has )Action set: On change > Refresh this Section), the customized message reverts to original.

Error Messages

Validation rule ones. E.g. "12.3 is not a valid integer value"

Steps to Reproduce

1. Write something in property so it will not pass validate.
2. Refresh this section through Action set.

Root Cause

An issue in the custom application code or rules as when the property is of type integer there is a implicit client side validation added on the field.

The error shown on blur of the input field is a client side validation and it uses the field value that was customized.

However when the refresh section happens, this integer property is submitted along, and server does dictionary validation for this integer property and adds an error.

​This server side error uses "IntegerValueBadFormat" message rule. Translating this message rule fixes the issue.


Perform the following local-change:

IntegerValueBadFormat to include local language for Server Side validation.

Published March 8, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us