In ArcGIS PRO allow formal edit sessions for unversioned data in an enterprise GDB

JohannaKraus1

ArcMap allows users to edit unversioned data in an enterprise geodatabase and choose whether edits will be automatically saved after each edit or evoke a formal edit session during which edits are stored before being committed/saved to the underlying database (giving users the ability to discard or undo unwanted edits). There are good reasons for maintaining unversioned data in an enterprise database and for being able to discard/undo edits – users should not have to choose between the two.

Please give users the option of a formal edit formal edit sessions for unversioned data in an enterprise geodatabase in ArcGIS PRO.

KoryKramer · ‎02-27-2023

@DavidWheelock2 "can it be made so that the user can make this setting persistent across sessions without having to wait for an admin to do it?" >>

Yes. Remember that the application management settings that can be controlled by an admin are only exposing options that are already available to the individual user. So in this case, any individual user can just go in and control the option themselves:

(Preview from development builds. The UI in 3.2 may be different.)

Now... if an admin sets this up a certain way and LOCKS the setting, then the individual will not be able to change it.

Does that answer your question? Is that what you meant by "persistent across sessions"?

DavidWheelock2 · ‎03-02-2023

Hi @KoryKramer.

What I'm suggesting is actually an improvement on ArcMap. Allow me to compare.

ArcMap

Let's summarize ArcMap behavior, first. In ArcMap the default when working with non-versioned SDE data is to automatically save edits immediately.

However, you can turn that off so that it will prompt you to save or discard edits at the end of the edit session. Even so, that setting only persists as an attribute of that MXD. So every time you open that MXD your setting will persist. However, if you open ArcMap fresh, without an MXD, then it defaults back to automatically-save and you have to turn that off yet again.

ArcGIS Pro

Currently ArcGIS Pro immediately auto-saves all edits to non-versioned SDE data without giving the user a way to turn that off.

I would like ArcGIS Pro to do at least what ArcMap currently does, but also to allow the user to turn off auto-save so that it persists through ALL edit sessions, without having to turn off auto-save every time you start a new project.

It sounds like that's what ESRI is doing with these changes but I just wanted to be clear.

⭐BONUS POINTS: It would also be really great if ArcGIS Pro could allow users to roll back individual edits within a non-versioned SDE edit session.

KoryKramer · ‎03-03-2023

>> It sounds like that's what ESRI is doing with these changes but I just wanted to be clear.

Yes, sounds like we're tracking 😊

>> BONUS POINTS: It would also be really great if ArcGIS Pro could allow users to roll back individual edits within a non-versioned SDE edit session.

This is not currently planned. We need to first provide parity for ArcMap user workflows and then we can evaluate Undo vs. full discard. To be clear, if this is needed in the future, it would be to Undo edits in reverse order, not pick an edit out of the middle of a stack and undo it.

Bud · ‎03-03-2023

BONUS POINTS: It would also be really great if ArcGIS Pro could allow users to roll back individual edits within a non-versioned SDE edit session.

This is not currently planned. We need to first provide parity for ArcMap user workflows and then we can evaluate Undo vs. full discard. To be clear, if this is needed in the future, it would be to Undo edits in reverse order, not pick an edit out of the middle of a stack and undo it.

@KoryKramer When the discard edits functionality gets released, will this idea be changed to "Implemented"? If so, will the idea for rollback/undo get lost in the shuffle?

In other words, do we need a separate idea for rollback/undo?

KoryKramer · ‎03-03-2023

@Bud Yes, given that this request is asking for the ArcMap functionality (which is discard) we plan to implement that and would close this idea at that time.

It would be more helpful if after the functionality is provided, users feel that additionally undo on nonversioned data is necessary, tracking that separately would be best.

Thanks

JenniferCadkin · ‎11-15-2023

This Idea has been implemented in ArcGIS Pro 3.2. Please see the What's New documentation for more new features in Pro 3.2.

The Your Ideas in ArcGIS Pro 3.2 blog and video have been posted to the Esri Community blog. You can take a look at these to see your idea and all others that were implemented in this release of ArcGIS Pro.

Here are two help topics to learn more:

https://pro.arcgis.com/en/pro-app/latest/help/editing/editing-options.htm

https://pro.arcgis.com/en/pro-app/latest/help/editing/enable-and-disable-editing.htm

PeteJordan · ‎09-06-2024

So it's been awhile and we've moved a dataset over from versioned to non-versioned on SDE for a few reasons.

Is the only current way (since the last part of this thread is close to a year old) to undo edits (similar to the <ctrl-z>) is to use the "single workspace edit session" and then each edit select your layer (if you have multiple, it's kind of a pain), edit one thing, if it's wrong, discard and repeat? Or do a few edits, and if one thing is wrong, do the same and then re-do everything you just did correctly?

I know this causes problems when something might be deleted by mistake or if a feature is split and you don't see the other segments, until a bit later, you would again have to discard all edits in that session and go back and redo them again?

Or is there something else I'm missing that has been introduced since Nov 2023, that we can now use the <ctrl-z> in a "Multiple workspace edit session" so that you don't have to keep selecting the layer to edit, edit, disregard all edits if a mistake is made and repeat"?

What have other people on here been doing since for their edit sessions? Another way is to just use a GDB and then keep importing that to SDE once inwhile so there is a full undo functionality again or go back to versioning which again we moved away from because of issues...