User Help > Working With Documents > Modifying a Document > Using Multiple-Row Editing > Summarizing Assumptions and Rules for Resynchronizing > Assumptions and Rules for Resynchronizing Client-Side Move Operations
  
Assumptions and Rules for Resynchronizing Client-Side Move Operations
Assumptions
There is no mechanism to resolve a node with an informational conflict icon because there is nothing to resolve. The message associated with this type of conflict is strictly informational.
Nodes with informational conflict icons can be moved, edited, and deleted.
Performing a second resynchronization on a document that has a node with an informational conflict icon clears this icon if it is the node’s only conflict.
Nodes displaying conflict navigation icons are not real conflicts. Consequently, clicking a node that has this icon does not display a conflict item header or the editable item preview.
Rules
If a moved node winds up with a different parent or previous sibling or path to the document root due to changes made on the server, the moved node has an informational conflict icon .
It is possible for a moved node with an informational conflict icon to also have an edit conflict icon . In this case, the edit conflict icon is shown in the row header. The icons for both conflict types are shown in the item header.
If you resynchronize again after resolving the edit conflict on a node that had both an edit conflict and an informational conflict, the edit conflict icon disappears. Only the informational conflict icon is shown.
If a node is moved on the client and moved to a different place on the server, an informational conflict icon is not shown. The rule in this case is that the last one is the winner.