sde edits by user who did not set up the project

[SarahRijneke]

Hello,

Curious if anyone can tell me a bit about what happens to data edits in an ArcGIS Pro project if one user sets up the project with features from their version and another user uses the same project to update the data. The editor can see the version of the person who set up the project in the data source tab. Every now and then we get database conflicts on the original users version and I'm wondering if this may have something to do with it.

[George_Thompson]

If the users (A & B) are using the same project (not at the same time), I would anticipate that you would see the version in the data source tab.

Now if you (user B) are editing on that same version and data, your edits would be in the same version as the other user A.

I could see how it may make conflicts in the version at times, if the same record is edited by both users A & B.

Is there a reason that you do not have a copy of the map and update the version to yours?

[VinceAngelo]

You need to go back and review the documentation on versioning. Versions stay forever, until deleted. They also pin subsequent edits in the A/D tables, making the geodatabase less efficient. This is not something which should be ignored.

If that initial set of edits in that version was just to prove it was possible, and never intended to be merged into the table, the version should be removed, and the state tree compressed, to eliminate the exact problems you're having now.

Versioned editing is a process, with primary use cases designed to incorporate the edits as quickly and efficiently as possible. Coloring outside the lines of best practice can stress the implementation and result in suboptimal performance.

- V