Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Conflict Detection and Resolution >

Merge Conflicts

A potential merge conflict arises when records are merged separately on both the Mobile Web Client and the database server. The following example illustrates the problem:

  1. On the Mobile Web Client, data from account A may be merged with account B.
  2. On the server database, data from account B may be merged with account A.
  3. Since delete transactions have the highest priority in Siebel Remote, this may lead to two delete transactions—one from the Mobile Web Client and one from the database server.
  4. In this case, data from both accounts will be deleted. To avoid this potential problem, do not merge data on Mobile Web Clients.


 Siebel Remote and Replication Manager Administration Guide 
 Published: 19 November 2003