Oracle CRM On Demand Desktop Administration Guide > How Oracle CRM On Demand Desktop Synchronizes Data > How Oracle CRM On Demand Desktop Synchronizes Data with Oracle CRM On Demand >

How Oracle CRM On Demand Desktop Synchronizes Data During the Initial Synchronization

An initial synchronization is a type of synchronization that occurs in the following situations:

• Immediately after the user installs Oracle CRM On Demand Desktop.
• If you make a metadata change to the user that includes a change to the customization package.
• If the options in the login dialog box change, for example, if the user name changes or the Oracle CRM On Demand URL changes.

The purpose of the initial synchronization is to initialize the Microsoft Outlook data storage with the Oracle CRM On Demand data that is available to the user. Oracle CRM On Demand Desktop downloads the customization package to Microsoft Outlook the first time the user synchronizes metadata with Oracle CRM On Demand.

How Oracle CRM On Demand Desktop Handles Errors During Metadata Download

If the current version of Oracle CRM On Demand Desktop is not compatible with the downloaded customization package, then Oracle CRM On Demand Desktop does not apply the package. Instead, it displays an error message to notify the user, and then records an entry in the general log file:

Logs\GeneralLog\log.####.txt

where #### are the assigned log numbers.

For information about where Oracle CRM On Demand Desktop stores this log file, see About Files, File Locations, and Profiles.

If an error occurs while the customization package is downloaded, then Oracle CRM On Demand Desktop displays an error message in the system tray. This error notifies the user that the customization package changed but Oracle CRM On Demand Desktop cannot download it because of certain errors. The problem might be because the user does not possess the required privilege on the Oracle CRM On Demand server. In this situation, the user must contact the system administrator to acquire the necessary privileges and then restart the synchronization. Also, the problem might be due to the fact that the user does not have the correct package published to that user's role, or the customization package might not have all the files needed. You must also check that the ZIP file for every customization package contains all the required metadata files, as you can have different packages for different roles.