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.

[JohnNergeBrooklynPark]

Nothing to add that hasn't already been said, just echoing support for this idea. Like others here, it's the one thing holding us back from a full scale Pro adoption.

[RufaroKaseke]

Echoing my support for this idea as well. Ran into this issue today and it's very frustrating.

[GIS_MJ]

I can't believe this hasn't been developed yet! I'm here to support this idea. ArcMap is still necessary without this functionality in PRO. 

[KeithAddison1]

This is a sickening situation.

[BrianOevermann]

Seems short sighted that we cannot create a "local" transaction that is not committed until we invoke a save. I anxiously await this capability.

[DavidCarpenter]

We are just about to deploy ArcGIS Pro 2.8.2 to the masses since the writing is on the wall for ArcMap and we need Pro for some of the newer Esri solutions we are looking to implement.  The fact that you are prompted to Save and review edits when working with File Geodatabases or Feature Services but not the Enterprise Geodatabase is truly insane.  Over the weekend we just had a very capable user who was under a serious time crunch doing selections and edits accidentally delete data from multiple layers, he eventually noticed what was happening and is now searching backups to fix his mistakes. 

Surely it can't be hard at a minimum to just expand the existing Save and Review functionality over to non-versioned Feature Classes in an Enterprise geodatabase?  Editing of any kind needs to be treated seriously and follow a formal workflow, at the end of the day we lived with clicking a Start Editing button this long and it wasn't that bad.  This needs to be changed ASAP...like 2.8.3 ASAP.

[JonathanMurphy]

We’re moving the status of this request to Under Consideration as the development team has an item for this work in their backlog.  To respond to the question about the level of effort, this will require a substantial amount of development work.  Since that work has not yet started, this functionality will not be in ArcGIS Pro 2.9.  We will update this idea’s status to In Product Plan when we have a higher level of certainty on when the development work can be prioritized into a release.  We hope that sharing this update helps inform your decisions about moving editing workflows to ArcGIS Pro.  Thank you

[DavidCarpenter]

Thanks so much for the response Jonathan, much appreciated.  I am glad to know you folks are looking into this, it has always been a point we questioned as we dabbled with Pro over the years but now that we are ready to implement having these experiences brought the concern to forefront.

[ChrisScheiner]

Really glad to see this getting attention, and to see the status change!

[larryy]

Hi All,

As Jonathan noted, we do have a backlog item to support the workflows suggested in this thread against nonversioned data.  We plan to get to that work in a future release.

In the interim, want to point out the ability to add a button to the Editor ribbon forcing the user to start an edit session before anything can actually be edited (or deleted in this case).  The help topic on it can be found here:  https://pro.arcgis.com/en/pro-app/latest/help/editing/enable-and-disable-editing.htm. 

Through the Editing tab on the Options dialog in Pro you can also enable the "Show dialog to confirm deleting data" checkbox as a second check for the inadvertent deleting of data.

Hope this helps.

Thanks, larry