Support Article
Explicit property mapping being eclipsed by default mapping
SA-2932
Summary
You observe Obj-Save fails when a class has explicit column mapping to a column of the same name as a property available to that object.
Error Messages
Cannot save instance of class myData-class1; it belongs to fully exposed table tb1 in database myDb, but the instance has properties which do not correspond to columns: anotherProp
Steps to Reproduce
- Create a superclass myData- with the property baseProp, and subclasses myData-class1 using a database table tb1, and myData-class2 using a database table tb2.
- In the myData-class1 ruleform, establish explicit mapping from the property anotherProp to column baseProp.
- Use obj-save to write a page of the class myData-class2 with a value specified for baseProp.
- Use second obj-save to write a page of the class myData-class1 with a value specified for property anotherProp.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. The explicit mapping should prevail over default mappings.
Resolution
This issue is resolved by hotfix item HFix-10199 which enforces that the external mapping prevails over the default mapping.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.