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

Property value is not saved in database

KCP-183

Summary



A property on the pyWorkPage is not saved in the database. The property is present in two classes which are in the same line of inheritance.


Error Messages



Not Applicable


Steps to Reproduce



Create a new case and check the property value saved in the database.


Root Cause



A defect in Pegasystems’ code or rules.
Having two properties with the same name, in a different font case (such as, all lowercase and camel case), and in the same class hierarchy, results in the incorrect property being mapped to the column.


Resolution



Perform the following local-change to populate the column:

Explicitly list the property and column mapping on the External Mapping tab of the class rule for the class in which the property is exposed.

Published December 2, 2021

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