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

Cannot save instance of class error



You, as an application developer, receive an error message when running an activity that sets property values and saves a record. The error message states the Status column does not exist but it is present in the database table.

Error Messages

Cannot save instance of class Sample-Data; it belongs to fully exposed table PRPC71.SAMPLE_DATA in database PegaDATA, but the instance has properties which do not correspond to columns: Status

Steps to Reproduce

1. Create a table.
2. Create a class and database table mapping.
3. Create properties which are part of database table.
4. Create an activity to set the properties, save, and commit the record to observe the issue.

Root Cause

The root cause of this problem is a defect in custom application code/rules. The Status property exists in multiple classes but was not specified on the External Mapping tab of the class rule.


This issue is resolved through the following local-change:

Add the properties to the External Mapping tab of the class rule
Suggest Edit

Published July 22, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

50% found this useful

Have a question? Get answers now.

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

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