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

Obj-save to external table fails after column added



After adding a column to an external table that Pega has a class mapped to, Obj-Save calls are failing.

Error Messages

Cannot save instance of class [Class]; it belongs to fully exposed table [Schema].[Table] in database [Database], but the instance has properties which do not correspond to columns: [Property]

Steps to Reproduce

Save an instance of [Class] through any activity.

Root Cause

As the node had not been restarted, the table metadata had not been reloaded, leading to the error.


Here’s the explanation for the reported behavior:

When a change is made to the DB table structure, one must either restart all nodes or re-save the corresponding Data-Admin-DB-Table or Data-Admin-DB-Name instance on all nodes.


Published May 27, 2016 - Updated October 8, 2020

Was this useful?

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