Each group in the target definition contains an attribute that determines the update strategy for the rows in that group. Configure the update strategy attribute in the mapping to specify the operation that you need to perform on the rows. You can perform INSERT, UPDATE, and DELETE operations on the rows. The default is INSERT.

The following table lists the valid values for the update strategy field for the parent group:

If you specify an invalid value for this field, the PowerCenter Integration Service treats the invalid value as INSERT. If you mark an entry for INSERT, the PowerCenter Integration Service treats the entry as INSERT. If the entry exists, the PowerCenter Integration Service writes an error into the session log. The session fails if the error count reaches the error threshold.

For child rows, an update operation is treated as replace. If a child row is marked for update, all values for the multi-valued attribute are replaced with the updated values. UPDATE AS UPDATE and UPDATE ELSE INSERT are skipped for child rows.

For example, consider an entry with a@infa.com mail attribute. You can add b@infa.com and c@infa.com as another mail attributes. As the child rows are marked for update, the entries b@infa.com and c@infa.com child rows will be marked for update. The rows in the target are replaced with b@infa.com and c@infa.com.

To reflect the changes made in the target, the PowerCenter Integration Service replaces the child rows marked for update with the changed values.

The following table lists the valid values for the update strategy for child group:

The naming convention for the update strategy field is Update_Strategy_<group_name>. The Parent_Group group contains the Update_Strategy_Parent_Group field, the ou group contains the Update_Strategy_ou field, and the mail group contains the Update_Strategy_mail field.

The following table shows the sample rows in the source ParentGroup_src:

The following table shows the sample rows in the source ou_src:

The following table shows the sample rows in the source mail_src:

In this example, each source represents a group in the target definition. To maintain key relationships when you connect mapping objects, connect the source columns to the corresponding group in the target definition.

The following table lists the column relationships between the source definitions and the groups in the multi-valued target definition:

The PowerCenter Integration Service inserts the following rows into the target definition:

For example, the base DN value for the LDAP target is ou=People, o=airius.com, and cn is selected as the primary key. If the value for the cn attribute is John, the DN value of the inserted entry is cn=John, ou=People, o=airius.com. Otherwise, the entry is inserted under the base DN selected for the target definition.