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

Integers with embedded spaces pass validation but cause an error



A developer notes that when an integer property is populated with a number that containts one or more spaces (e.g. "12345 67890") the following error is produced:

Fail ** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)

This should not pass validation, instead of failing during the integer conversion.

Error Messages

Fail ** PropertyValueInvalid null .pegaToInteger() Invalid number format (was 12345 67890)

Steps to Reproduce

Create an integer propery in a section and enter a number that includes space.

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. There is a failure to detect embedded spaces in an integer during screen validation.


This issue is scheduled to be resolved in Maintenance Level (ML) release 7.1.7

Published January 31, 2016 - 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