Siebel Remote and Replication Manager Administration Guide > Troubleshooting Remote and Replication Manager > About Merge Conflicts Related to Assignment Manager >

Distinguishing Between Harmless and Meaningful Merge Conflicts


The following procedure describes how to distinguish between harmless merge conflicts caused by changes to ASGN_DT fields, and conflicts that do involve your data. For an explanation of the cause of merge conflicts involving ASGN_DT fields, see About Merge Conflicts Related to Assignment Manager.

To distinguish between harmless and meaningful merge conflicts

  1. Using the Mobile Web Client, from the application-level menu, choose Navigate > Site Map > User Preferences > Remote Status.
  2. In the Remote Status list, select a synchronization session record that interests you.
  3. In the Session Actions list, select a record that has the following value in the Item Name field:

    Apply database changes

  4. In the Session Action Details list, inspect the messages in the Item Details field.

    Table 31 describes how to interpret these messages.

Table 31.  Interpretation Guidelines for Synchronization Conflict Messages
Item Details Message Characteristics
Guideline

Identifies who updated the record. For example, "Updated by HKIM."

Identifies a visible data field. For example, "Field: Product Under Warranty Flag, New Value: Y, Old Value: N"

Meaningful. Inspect server and client values to determine whether conflict was resolved appropriately.

Does not identify who updated the record. For example, "Updated by ?"

Identifies an Assignment Date field. For example, "Field: Assignment Date, New Value: 2003-11-04 11:09:18.000000, Old Value: 2003-10-25 10:10:02.000000"

Safe to ignore.

Siebel Remote and Replication Manager Administration Guide