Unable to edit anything from a dataset since a feature class was added to it using Pro

JS_GilbertAZ · ‎01-19-2023

I have a question about Pro / ArcMap compatibility, we are using SDE 10.8.1 and ArcMap 10.8.1, and I added a new feature class to one of our datasets using ArcGIS Pro 3. That dataset now caused problems for ArcMap editors, if they have anything in that dataset in their project, they cannot edit, not even editable layers in other datasets, they just get an error that there are no editable layers. Remove the layers in that dataset from ArcMap, and all other layers can be edited fine. The ones in the "offending" dataset can be edited fine in Pro. I double checked the versioning in Pro, it's set to traditional versioning. ArcCatalog shows that the dataset is registered as versioned also. I can't find anything in ArcMap/ArcCatalog that indicates that the data is not available to be edited. All permissions are there also.

Did this get caused because when I added the feature class to the dataset in Pro, it "upgraded" the dataset and now is not editable in ArcMap? I've been looking for documentation on this but haven't been able to find any.

Unfortunately we still have to use ArcMap for some processes, as some of the software we interact with doesn't support Pro yet. Thankfully the dataset that is affected doesn't need to be edited with ArcMap, but I am just trying to find out if this is something that I will need to be careful of going forward, at least until ArcMap is no longer used.

Thanks in advance for any knowledge / info that you can provide on this. If this is documented somewhere, I missed it...

Jeff

DougGreen · ‎01-19-2023

Even though you are adding a feature class to a feature dataset that was previously registered as versioned, I believe the newly added feature class is not registered as versioned. I think you have to free locks and register the feature dataset as versioned again.

JS_GilbertAZ · ‎01-23-2023

I did that after I added the feature classes, all is registered as versioned. One thing I did find out is that the annotation one that I added is the one that's causing the problem.