User Help > Working With Documents > Modifying a Document > Using Multiple-Row Editing > Resynchronizing Documents During Multiple-Row Editing > Deleting a Node that Has an Edit Conflict After Resynchronizing
Deleting a Node that Has an Edit Conflict After Resynchronizing
After resynchronizing, you can choose to delete a node with an edit conflict. The following list describes behaviors associated with deleting a node that has an edit conflict:
The deleted node behaves as a pending delete, respecting the Show Pending Deletes option to determine whether to display the item in the Document view. For more information, see Showing and Understanding Pending Deletes During Multiple-Row Editing.
When the deleted node is shown, the conflict icon no longer displays. The node displays in light gray type, and aRemoved label replaces the section number. The edited field icon displays in the row header, If there is enough room, the deleted item icon also displays.
If you save your changes, the deleted node is not considered an unresolved edit conflict when determining whether the save is possible.
If you undo the deletion of a node that had an unresolved edit conflict, the node no longer behaves as a pending delete. Consequently, the node shows regardless of the Show Pending Deletes option. Additionally, the unresolved edit conflict displays once again on the node.
Deleting the child of an undeleted delete conflict does not remove the conflict on the parent item. If you then delete the parent, the conflict on the parent is removed. Undoing the parent deletion restores the parent conflict but not the child conflict. Undoing one more time restores the child conflict.
If the client shuts down unexpectedly, the node appears in its last known state in the recovered view.