You should the model group path patterns when working with nested business objects that are part of a model group.
<?xml version="1.0" encoding="UTF-8"?> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://MultipleGroup"> <xsd:complexType name="MultipleGroup"> <xsd:sequence> <xsd:choice> <xsd:element name="child1" type="Child"/> <xsd:element name="child2" type="Child"/> </xsd:choice> <xsd:element name="separator" type="xsd:string"/> <xsd:choice> <xsd:element name="child1" type="Child"/> <xsd:element name="child2" type="Child"/> </xsd:choice> </xsd:sequence> </xsd:complexType> </xsd:schema>Note that there can be multiple instances of the elements named "child1" and "child2",
You should use the Service Data Object (SDO) path patterns for model groups to resolve these conflicts.
set("child1/grandchild/name", "Bob"); set("child11/grandchild/name", "Joe");