What is updating geodatabase default version?

[JimSmith]

Environment: ArcGIS 10.1, ArcSDE Geodatabase 10.1, SQL Server 2008R2

User is editing a feature class registered as versioned with move to base option. She sometimes gets the following message when trying  to save edits:

"Your edits could not be saved because the target version has been updated since you started editing. These edits have been merged into your edit session. Review the changes and save again."

As far as we know she is the only editor at that time. The Geodatabase is used as a project workspace for geoprocessing data by 6-10 users. That includes the possibility that other users are creating new feature classes, altering table schema in existing feature classes, or performing bulk load operations - in default - while the user is editing. Can any of the other users' actions result in changes to default and cause the message?

I think the short answer is "use fully versioned workflows" but need clarification on what constitutes an "update" to default version - it's not in the training book.

Thanks!

[RobertScheitlin__GISP]

Jim,

   We get that message when another one of our editors has map changes to a featureclass and saved their edits before the other user has saved theirs.

Can any of the other users' actions result in changes to default and cause the message?

Yes.

So it sounds like there was some edit that occurred and was saved before your editor has saved their changes. You would not get this message otherwise.

[AsrujitSengupta · Accepted solution]

This should give you a good idea as to why that warning (its not an error message) is observed.

32352 - How does the state tree change during an edit session?‌

To suppress message if no conflicts exist, the below change can be made in ArcMap:

1. Open the ArcMap session
2. Select Editor on the Editor Toolbar.
3. Click Options.
4. Click the Versioning tab
5. Click the "Automatically save changes only if there are no conflicts" radio button

ArcGIS Help (10.2, 10.2.1, and 10.2.2)‌

[JimSmith]

Correction to my post: an explanation of multiple editors using move to base (MTB) option is in the ESRI course workbook, Lesson 10, and there on page 10-8 is the very same warning message:

"Your edits could not be saved because the target version has been updated since you started editing. These edits have been merged into your edit session. Review the changes and save again."

This is because when using the MTB option the edits are no longer isolated after they have been saved... the target version, Default, has been updated... so, when two users change Default at the same time, the second editor to save must do an implicit reconcile (first save) and then an implicit post (second save after message) in order to move the changes to the base tables.

Above responses are both correct in identifying the cause (Robert) and the fix (Asrujit). We have multiple editors and update scripts applying changes to Default version. We have asked the users of this Geodatabase to set versioning to "Automatically save changes..."