When performing undo and redo operations for a tree node deletion, a new TreeID is used due to the associated Data MapContainer.
However, concurrent operations might bring back the deleted node while keeping its original TreeID. This results in the node having two IDs in the undo manager: the original and the newly created one from the redo.
To address this, we need to remove the bring-back node from the remapping when importing.
When performing undo and redo operations for a tree node deletion, a new
TreeIDis used due to the associated Data MapContainer.However, concurrent operations might bring back the deleted node while keeping its original
TreeID. This results in the node having two IDs in the undo manager: the original and the newly created one from the redo.To address this, we need to remove the bring-back node from the remapping when importing.