Siebel CRM Desktop for Microsoft Outlook Administration Guide > How Siebel CRM Desktop Synchronizes Data > Factors That Determine Which Data Siebel CRM Desktop Synchronizes >

How Siebel CRM Desktop Avoids Duplicate Data

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

• The standard user keys included in the Siebel database
• The option to implement data deduplication that you can deploy to prevent duplicate data

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

Siebel CRM Desktop also supports configuration of user keys in the metadata for the client. If Siebel CRM Desktop detects a Microsoft Outlook insert during synchronization, then it does the following work:

• Queries the synchronization object in the Siebel database with the user key to determine if there are any existing records that match the record being inserted.
• If Siebel CRM Desktop does not find a match, then it proceeds with the insert operation.
• If Siebel CRM Desktop finds a match, then it raises a synchronization issue that prevents the insert.