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.
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.
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.