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 class instance that belongs to a fully exposed table



declare index rule displays an error which states that the instance has properties which do not correspond to the columns: customerid. This occurs even when the column exists in the user's table and is already optimized.

Error Messages

pyCommitError: Can not save instance of class Index-CEP-Work, it belongs to fully exposed table pegadata.Index-WTW-CEP-Work in database Pega DATA, but the instance has properties which do not correspond to columns : customer id

Steps to Reproduce

  1. Create a table.
  2. Create a class and database table mapping.
  3. Create properties which are part of the database table.
  4. Create an activity to set the properties.
  5. Save the activity.
  6. Commit the record.

Root Cause

An issue in the custom application code or rules.
The customerid property existed in multiple classes, but was not specified on the External Mapping tab of the class rule.


Perform the following local-change:
Add the properties to the External Mapping tab of the class rule.

Published August 19, 2019 - Updated December 2, 2021

Was this useful?

33.333333333333% 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