Manually resolve conflicts with Check In / Check Out Replicas does not seem to work without versioning

Stefan_Offermann — Fri, 06 Dec 2024 13:44:20 GMT

I have setup an Oracle 19C database with ArcGIS Pro 3.4 and created a feature dataset with a polygon feature class. I have a text field which contains a remark. I do not activate (traditional) versioning because it is always a source of slow database behaviour with my users.

I wanted to test conflicting edits like "Update-Update" in two Replicas. I created both Replicas with in_type = "CHECK_OUT" as local File Geodatabases. My feature has a value of Remark = A in the parent replica (Oracle). I opened the child replicas in two new maps. In the first Replica, I updated the Remark to B1. In the second Replica, I updated the Remark to B2. I saved both edits in both File Geodabase child replicas. Then I synchronize the edits back to the parent Replica in the Oracle Database:

Geodatabase 1 = Oracle SDE
Geodatabase 2 = One of the two FGDBs containing the conflicting edits
Direction = From geodatabase 2 to geodatabase 1
Manually resolve conflicts <-- this does not seem to work!
Conflicts defined by column

My expectation was: When I sync second Replica back to the SDE, a conflict would emerge, because the first Replica set Remark from A to B1, while my second Replica would set Remark from A to B2.

What happened instead: Without any conflict, the second sync set Remark to B2. The value of B1 gets overwritten without further notice.

Am I missing something? Does conflict management require activated Versioning on my data?

topic Manually resolve conflicts with Check In / Check Out Replicas does not seem to work without versioning in Data Management Questions

Manually resolve conflicts with Check In / Check Out Replicas does not seem to work without versioning