Support Article

Property value is not getting saved to the database



After upgrading from PRPC 5.x to Pega 7.2, the database (DB) column for an exposed property is not being populated.

Error Messages

Not Applicable

Steps to Reproduce

Create or update an instance of a class in which the affected property is used and exposed, giving the property a value.

Root Cause

A defect in Pegasystems’ code or rules, where having two properties with the same name in different cases (such as all lowercase and camel case) in the same class hierarchy can result in the wrong property being mapped to the column.


Perform the following local-change:

Explicitly listing the property and column mapping on the External Mapping tab of the class rule for the class in which the property is exposed will allow the column to be populated.

​The underlying issue is slated to be addressed in a future release of the Pega Platform.

Published February 28, 2017 - Updated March 16, 2017

Have a question? Get answers now.

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