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

External class mapping does not work



User is noticed the same symptoms as described in the below link.

However, the local change in the resolution (Saving the property with name matching the database column to class mapped to database table) does not resolve the issue.

Error Messages

Instance has a property that does not correspond to column.

Steps to Reproduce

1. Create an external class mapping rule.
2. Add a column to the database table and the map a different in Pega.
3. Create and activity and run it then the issue will be appearing.

Root Cause

A defect in Pegasystems’ code or rules, implicit mapping was taking precedence over specified explicit external class mapping.


Perform the follwoing local-change steps(without hotfix):

1. Create Table that has column COL1.
2. Include Class with properties COL1 and ABC.
3. Map Column COL1 to property ABC via class mapping tab in class definition.
4. Create declare trigger rule for property COL1 with settings as TRIGGER WHEN AN INSTANCE IS “Commited Save”.

Without the above Step 4. rule, an exception is thrown when record is saved.
With the above Step 4. rule, the value of column COL1 is updated with value of property ABC (as expected).

Suggest Edit

Published March 24, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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