Hello! We have just set up a new database with sde-schema (on a SQL server) which we edit using Versioning. We use Traditional versioning in ArcGIS Pro version 3.0.3. Just to verify the database and the functions we would like to force a conflict. However, it seems that we cannot create any conflicts. The button Conflict Manager is always greyed out and we never receive any warnings of any conflict. All the other buttons are working as they should. Ways that we have tried to generate conflicts: Two different EDIT versions created by two different users with the same privileges. Editing the same object (one deleting it, one changing geometry, placement or attribute). Then, reconciling and posting the changes. One different EDIT version created. Edits being made in the target (DEFAULT) version at the same time as edits being made in the newly created version. Both editing the same object. Then, reconciling and posting the changes. Saving edits, reconcile, post in different order to force a conflict. No conflicts detected when trying the different actions in different order. Changing the settings of how to define conflicts and how to resolve conflicts. Using Enable and disable editing from the Edit tab. With no different result. The only message we receive (below) is when we are changing between DEFAULT version and EDIT version without posting the changes first: What are we doing wrong? Have we missed something when setting up the database? Also, when opening the Version Changes and Differences view, nothing is shown in the list even though we have made many EDIT versions and edit changes. Any clue as to why we don’t see anything here? Thanks in advance!
... View more
