Siebel Server Sync Guide > Administering Siebel Server Sync > SSSE Domain Mapping >

About Resolving Synchronization Conflicts

If data in the Siebel application and Microsoft Exchange Server has been modified in such a way that SSSE cannot synchronize the differences, the current version of SSSE always resolves the conflict by using the data from the Siebel application.

An example of a synchronization conflict might be that the Status of an Exchange Task was set to a value that differs from the value of the corresponding Siebel To Do item. If the status was updated at approximately the same time, thereby falling within the same synchronization cycle, SSSE has no way to determine which update should be applied, and automatically uses the data from the Siebel application.