I wanna ask about peer-to-peer replication. When i’m create peer-to-peer replication, i’m using 2 nodes that can pull and push subscription (multi-master). When it works until i’m updating, insert, or deleted it. The problem is when i’m got conflict detection cases. When i’m using Update/Delete case. From node 1 is update, but when in node 2 is delete. It’s got conflict. When we check in Conflict Detection Viewer. It still conflict and not resolved. 

I’m already start enable conflict detection. and pointing originator_id from node 1. Do you have any solution for this. In my opinion, could it be set if this case is multi-master, keep the parent data from originator_id from node 1, not from node 2. So the data from node 1 is not in accordance with node 2. 

Maybe could you help my problem, 
Thanks

​I wanna ask about peer-to-peer replication. When i’m create peer-to-peer replication, i’m using 2 nodes that can pull and push subscription (multi-master). When it works until i’m updating, insert, or deleted it. The problem is when i’m got conflict detection cases. When i’m using Update/Delete case. From node 1 is update, but when in node 2 is delete. It’s got conflict. When we check in Conflict Detection Viewer. It still conflict and not resolved. I’m already start enable conflict detection. and pointing originator_id from node 1. Do you have any solution for this. In my opinion, could it be set if this case is multi-master, keep the parent data from originator_id from node 1, not from node 2. So the data from node 1 is not in accordance with node 2. Maybe could you help my problem, Thanks  Read More

​