Cannot save class instance that belongs to a fully exposed table
A 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.
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
- Create a table.
- Create a class and database table mapping.
- Create properties which are part of the database table.
- Create an activity to set the properties.
- Save the activity.
- Commit the record.
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.