Summary

The Property-Remove method behaves incorrectly on the Embedded Page and Embedded Page List property which are configured to refer a data page. The attached application shows how the standard Embedded Page and Page Lists properties react to the Property-Remove method call and how those which are configured to refer a data page react to the same method call.

1. TestMyList is an embedded Page List property which refers the Data Page - Property-Remove method calls on this aggregates embedded Page Properties have no effect
2. MyList_1 is a standard embedded Page List property - Property-Remove method calls on this aggregates work as expected except when OperatorAccount is removed. This is an embedded Page property which refers a data page. However, the property remains on the Clipboard with only the pxObjclass set
3. MyOther is a standard embedded Page - Property-Remove method calls. The composite work is as expected except when OperatorAccount is removed. This is an embedded Page Property which refers a data page. However, the property remains on the Clipboard with only the pxObjclass set

Error Messages

Steps to Reproduce

1. Create an embedded Page List property and name it TestMyList. It must refer to Data Page - Property-Remove method calls on this aggregates embedded Page properties have no effect
2. Create a standard embedded Page List property and name it MyList_1- Property-Remove method calls. This aggregates work correctly. However, when the OperatorAccount is removed, the embedded Page property refers to a data page. The property remains on the Clipboard with only the pxObjclass set
3. Create another standard embedded page and name it MyOther  - Property-Remove method calls. The composite work is as expected except when the OperatorAccount is removed. This is an embedded page property which refers to a data page. However, the property remains on the Clipboard with only the pxObjclass set

Root Cause

Resolution