Siebel Server Sync Guide > Siebel Server Sync for Microsoft Exchange Server Architecture Overview >

About Synchronizing Records During the Ongoing Extract Process

This topic describes record synchronization during the ongoing extract process. For information on the initial extract process, see About Synchronizing Records during Initial Extract and About SSSE Contact Record Matching.

The ongoing extract process is similar to the initial extract process but differs in the following respects:

• The only record changes that ongoing extract evaluates are the changes that have taken place since the last time the user was successfully synchronized.
• If a Siebel record and a Microsoft Exchange record were associated with each other in a previous synchronization, key fields are not used to determine what action to take. Instead, record IDs are used when determining whether a Siebel record or Microsoft Exchange record has changed. This allows users to change values in key fields while preserving the association between a Siebel record and a Microsoft Exchange record.
• If a record changes in both the Siebel environment and the Microsoft Exchange environment between synchronizations, SSSE treats the situation as an update conflict. The changes in the Siebel environment are preserved and the Microsoft Exchange environment inherits these changes through synchronization.

  NOTE:  You can change the SSSE default behavior so that when update conflicts occur, the changes in the Microsoft Exchange environment are preserved and are written to the Siebel environment. For information, see Changing SSSE Default Values For Synchronization Conflicts.

• In general, if a record is modified in one environment but is deleted in the other, then the record is deleted in the remaining environment at the next synchronization. However, the behavior differs slightly depending on which domain is involved, where the deletion occurs, and when the deletion occurs, as follows:
  • If a Siebel contact, task, or calendar record is synchronized with Microsoft Exchange and the user deletes it in Microsoft Exchange before that user's next synchronization occurs, then the next synchronization does not delete or otherwise affect the Siebel record.
  • If, instead, the user's data is synchronized successfully at least once between the initial synchronization to Microsoft Exchange and the deletion of the record in Microsoft Exchange, then the results are as described as follows:
    • If a user deletes a contact record in Microsoft Outlook that has the Private check box selected, then SSSE deletes the corresponding Siebel personal contact record.
    • If a user deletes a task in Microsoft Outlook, then SSSE deletes the corresponding Siebel task record.
    • If a user deletes a contact record in Microsoft Outlook that does not have the Private check box selected, then SSSE removes the user from the Sync List for the corresponding Siebel business contact record.
    • If a user deletes a contact record in Microsoft Outlook that has the Category field set to Employee (or PIM Category Value for the Employee domain), or if the Category field is cleared, SSSE makes no changes to the corresponding Siebel record because the Employee domain is configured for one-way synchronization, from the Siebel record to the Microsoft Exchange record.
• The Category field for a Microsoft Exchange contact record must contain an appropriate value in order for the record to be synchronized with the Siebel database. Depending on the values in the Category field and whether or not the Private check box is selected, the Siebel record that corresponds to a synchronized Microsoft Exchange contact record can be any of the following Siebel record types:
  • Siebel business contact record
  • Siebel personal contact record
  • Siebel employee record

For more information about how Microsoft Exchange Category field values and Private check box status affect corresponding Siebel record types, see Table 11.