Oracle CRM On Demand Desktop Administration Guide > How Oracle CRM On Demand Desktop Synchronizes Data > Factors That Determine Which Data Oracle CRM On Demand Desktop Synchronizes >

How Oracle CRM On Demand Desktop Avoids Duplicate Data

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

• The standard user keys included in the Oracle CRM On Demand database.
• The option to implement data deduplication that you can use to prevent duplicate data.

To define the data structures that are available to synchronize with Microsoft Outlook, Oracle CRM On Demand Desktop uses Oracle CRM On Demand object metadata definition. The object metadata definition supports the definition of a user key, which is the first additional layer of duplicate prevention.

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

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