Siebel Remote and Replication Manager Administration Guide > Configuring the Siebel Server > Process of Configuring System Preferences for the Siebel Server >

Configuring System Preferences for Resolving Conflicts

This task is a step in Process of Configuring System Preferences for the Siebel Server.

This topic describes system preferences that you can configure to resolve conflicts.

Setting the Intersection Table Conflict Resolution Field

If a record that is involved in an insert conflict is associated with extension records and child records, then the extension records and child records undergo the same conflict resolution process as the parent record. To view the results of conflict resolution operations in the local database, the user can navigate to the User Preferences screen, and then the Remote Status view.

CAUTION:  For important caution information about setting the Intersection Table Conflict Resolution field, see Caution About Extracting the Server Database.

To set the Intersection Table Conflict Resolution field

• Set the Intersection Table Conflict Resolution field to one of the following values:
  • First In. Keeps the existing record and the associated extension records and child records. Discards all values from the record for which Siebel Remote attempted an insertion. It also discards the associated extension records and child records of this record.
  • Last In. Replaces the existing record with the record Siebel Remote is inserting. Replaces the associated extension records and child records of the existing record with those of the record Siebel Remote is inserting.
  • Merge. (Default value) Combines values from these records and their extension records and child records. Exact behavior depends on which fields Siebel Remote populates with non-NULL values and on the value of the Intersection Table Merge Rule system preference. For more information, see Setting the Intersection Table Merge Rule Field.

Intersection Table Conflict Resolution with Various Siebel Releases

In releases earlier than Siebel CRM version 7.7, Siebel CRM handled an insert conflict on an intersection table by creating a duplicate record with a nonzero value in the Conflict ID field. Beginning with Siebel CRM version 7.7, you can choose between available values for this preference to determine how Siebel CRM handles insert conflicts on intersection tables in enterprise, regional, and local databases. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server.

Setting the Intersection Table Merge Rule Field

The Intersection Table Merge Rule field depends on the value that you choose in the Intersection Table Conflict Resolution field:

• If the Intersection Table Conflict Resolution field contains a value of Merge, then the Intersection Table Merge Rule field determines which field values survive when Siebel Remote merges two records to resolve an insert conflict on an intersection table.
• If the Intersection Table Conflict Resolution field contains a value other than Merge, then Siebel Remote ignores the Intersection Table Merge Rule field.

CAUTION:  For important caution information about setting the Intersection Table Merge Rule field, see Caution About Extracting the Server Database.

For more information about resolving insert conflicts, see Setting the Intersection Table Conflict Resolution Field.

To set the Intersection Table Merge Rule field

1. Set the Intersection Table Conflict Resolution field to Merge.
2. Set the Intersection Table Merge Rule field to one of the following values:
   • First In. (Default value) Siebel Remote applies the following rules to fields in parent records, child records, and associated extension records:
     • New, non-NULL values always replace existing NULL values
     • Existing, non-NULL values are always preserved
   • Last In. Siebel Remote applies the following rules to fields in parent records, child records, and associated extension records:
     • New, non-NULL values always replace existing NULL values and non-NULL values.
     • Existing, non-NULL values are preserved if the corresponding new value is NULL.