Came across this after moving to Pro and thought I would put this out there for anyone else that might find it useful. When editing an enterprise geodatabase in ArcMap on a non-versioned feature class I would get an error like this:
![Non-versioned.PNG Non-versioned.PNG](https://community.esri.com/t5/image/serverpage/image-id/110690iBFE1DAA197A394E0/image-size/large?v=v2&px=999)
To get around this error you needed to go into the Editing Options from the editor toolbar dropdown and uncheck the toggle to 'Edit a version of the database with the ability to undo and redo':
![Editing Options.PNG Editing Options.PNG](https://community.esri.com/t5/image/serverpage/image-id/110692i7BF02A71DB1FE0B5/image-size/large?v=v2&px=999)
I was looking for a way to do this in ArcGIS Pro 3.2 because when trying to calculate a field from a joined table I was getting this error:
![error calculating field outside edit session.PNG error calculating field outside edit session.PNG](https://community.esri.com/t5/image/serverpage/image-id/110696i74549F39704549F7/image-size/large?v=v2&px=999)
With some help from Derek Nelson and the product team at ESRI it was found that the way around this in ArcGIS Pro is to do two things before trying the calculation (otherwise it puts the data in a strange state that does not allow you to perform the calculate field option): Go into your editing options dialog by selecting the small expand button in the lower right corner of the Manage Edits section of the Edit menu and turn off both 'Enable and disable editing from the Edit tab' AND 'Enable Undo toggled on by default'...
![Enable edits from the edit tab.PNG Enable edits from the edit tab.PNG](https://community.esri.com/t5/image/serverpage/image-id/110697i77C28012937F7926/image-size/large?v=v2&px=999)
![Undo on by default.PNG Undo on by default.PNG](https://community.esri.com/t5/image/serverpage/image-id/110698i3D31C7AF7606F983/image-size/large?v=v2&px=999)
This allowed me to perform the calculation and since the data is non-versioned it applied the change immediately and did not prompt me to save the edits as the calculation was done outside of an edit session with the ability to undo and redo. Make note of that, the changes get applied to the non-versioned data and cannot be undo in a single operation.
I hope that this post is found to be accurate and useful to the users out there. It worked for me!