Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Conflict Detection and Resolution >

Insert Conflicts

Although a user may successfully add a database row to a client database (or the server database), the added (or inserted) transaction may duplicate a new entry in another database residing elsewhere and not yet processed by the server. Siebel Remote determines that an insert or duplicate conflict exists when a new row's user primary key matches that of an existing row.

Because Siebel Remote cannot determine whether the transaction is a true duplicate or simply an erroneous use of the same identifier for two different data entities, Siebel Remote cannot ignore the duplicate transaction. Instead, Siebel Remote adds the new row and sets the column CONFLICT_ID, which is normally Zero, to the record's ROW_ID. This both indicates that the row is a duplicate and assures a unique value for the _U1 index. The mobile user can determine whether an insert conflict (also sometimes called a duplicate conflict) has occurred by consulting the Remote Status view and by watching for duplicates in regular data views, such as Accounts or Contacts.

For example, the user might change the user primary key and resubmit the update. As the user resolves the conflict, Siebel Remote captures the database update for transmission to, and resynchronization with, the server during the next synchronization session.

NOTE:  The local database treats null as a unique value and consequently allows duplicates if you leave a key field null for two or more records.

The system administrator must monitor and resolve conflicts created on the server. The conflicts are visible as duplicate records in regular data views such as Accounts or Contacts. To resolve an insert conflict, you can perform a merge on the duplicate records using the user interface Merge Record feature (Edit > Merge Records). The Merge Records option is enabled only after you select more than two records in the applet.

You can also change the user keys of one of the duplicate records to resolve the conflict.

Until these conflicts are resolved, EIM cannot be used to merge the records, since the conflict flag is not reflected in the interface table columns.