How Siebel CRM Desktop Avoids Duplicate Data

Siebel CRM Desktop includes metadata in the client and configuration in the Siebel Runtime Repository that prevents it from creating duplicate data. This configuration is in addition to the following items:

• The standard user keys that reside in the Siebel database.

  Data deduplication that you can deploy to prevent duplicate data. For more information, see Resolving Synchronization Conflicts.

• The view mode that Siebel CRM Desktop uses for duplicate requests during synchronization for an object type. For more information, see Controlling the View Mode During Synchronization According to Object Type.

Siebel CRM Desktop uses Siebel integration objects to create the data structures that are available to synchronize with Outlook. These objects support the user key definition that is the first additional layer of duplicate prevention. For information about how to configure user keys for integration objects and how the EAI Siebel Adapter uses them, see Overview: Siebel Enterprise Application Integration.

Siebel CRM Desktop also supports user key configuration in the metadata for the client. If it detects the Outlook insert during synchronization, then it queries the synchronization object in the Siebel database with the user key to determine if any records exist that match the record that it is inserting. If it:

• Does not find a match. It proceeds with the insert operation.

• Finds a match. It raises a synchronization issue that prevents the insert. For more information, see Resolving Synchronization Conflicts.