Pro > ArcMap editing capabilities?

[RoseF]

When we upgraded to 3.0, we noticed that if someone had edited a GDB in Pro v3.0, it was no longer editable in ArcMap. We think it has something to do with annotation layers. Is this an intentional/expected outcome? We have noticed since the v3.1 release that this issue persists. 

[JenniferCadkin]

Annotation will need to be upgraded to be editable at ArcGIS Pro 3.0.  The linked help topic includes a table that describes annotation support. 

https://pro.arcgis.com/en/pro-app/3.0/tool-reference/data-management/upgrade-dataset.htm 

[RoseF]

Yes, we would have had to upgrade our annotation for use in 3.0 (as well as for 2.x for that matter). For this reason, we had anticipated NOT being able to edit the annotation feature classes, but the restriction is on ALL feature classes in the geodatabase. I believe we were trying to edit a polyline feature class and a polygon feature class. We will do some additional testing now that 3.1.x has been released to see if this is still an issue.

[TonyContreras_Frisco_TX]

Do you get any kind of error message? If your edits resulted in utilizing newer functionality that is not available in ArcGIS Desktop, that might be the cause. See this info for more details. Later in the same page it lists datasets that are not supported before version 3.0 of ArcGIS Pro, which would include any Desktop  version. If none of that applies, you could try using ArcGIS Desktop (ArcMap or ArcCatalog) to copy the data to a new, empty fgdb and see if that data can be edited. Also make sure they data is not locked by another user or application before you attempt to edit.

[RoseF]

Thanks for the response! Yes, we were getting an error message in Pro 2.x but it was something very vague like, "this GDB cannot be edited". It wasn't until we opened it in ArcMap and tried to edit that we got an error that specifically said the annotation feature class was the layer that was uneditable. Even though we hadn't even added that feature class to our MXD. To solve the problem, we did exactly what you said and copied everything into an empty FGDB except for the annotation feature classes. It's just that this takes a lot of time when you have to do it for multiple projects and multiple team members.

I'm confident that we made sure the data wasn't locked by another user. We made copies of the original FGDB to different locations on our network, our local computers, etc and had no luck.