InsertLeaves Method

Use InsertLeaves to insert records into the Siebel database. When InsertLeaves is called on an integration object hierarchy, the EAI UI Data Adapter inserts leaf nodes only and uses internal nodes for maintaining parent-child relationships:

• Internal Nodes. All internal nodes must already exist in the database and Row Id must be specified (Row Id is the implicit, hard-coded user key used by the EAI UI Data Adapter). If the internal node does not exist or Row Id is not specified, then the EAI UI Data Adapter returns an error. For more information about user keys, see About the EAI UI Data Adapter Business Service.

• Leaf Nodes. Whether or not Row Id must be specified for leaf nodes depends on the type of integration component:

  • If the integration component represents a normal business component or MVG business component, Row Id must not be defined, because records for these components are being inserted.

  • If the integration component represents an association business component or an MVG association business component, leaf nodes might or might not have Row Ids defined. If Row Ids are specified, then the EAI UI Data Adapter creates an association record only. If Row Ids are not specified, then both a child record and an association record are created.

InsertLeaves returns an integration object hierarchy. Each integration component instance in the hierarchy has two fields: Row Id and Mod Id (implicit status keys used by the EAI UI Data Adapter). You can use these fields to retrieve the Row Id of the newly created record.