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 in the work object is not getting saved to the database



An exposed property is not getting saved to the database column, although it is properly being saved to the BLOB.

Error Messages

Not Applicable

Steps to Reproduce

  1. Define a property XY in child class P-c and expose the property in class P's table. Observe that proper column population is occurring.
  2. Determine that other subclasses of P need access to the property, for example P-c2, so define the property in parent class P but accidentally give it the wrong case, for example Xy. Observe that populating of the property in the table is no longer occurring.
  3. Attempt to remedy the situation by withdrawing property Xy in parent class P and defining correct case property XY. Observe that column population is still not occurring.

Root Cause

Withdrawing the wrong case property was insufficient.


Deleting the property from the database allowed the exposed column to be populated properly. In the example described above, deleting property Xy from the database resolved the issue.

Published January 5, 2017 - 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