Annotation Feature Class Data Model changes different ArcMap / ArcGIS Pro Versions

JamesMorrison1

Hello Everyone

Has anyone else issues with Annotation Feature Class Data Model changes between different ArcMap / ArcGIS Pro Versions loaded over the years into Oracle eGDB / SDE 10.6, 10.7, 11.0, 11, 1

I'm finding it quite difficult to track down each data model per version. To compare data models.

Any help or info? 

Thank you

MMBR

Hello @JamesMorrison1 

I am adding these links to help with the discussion.

Annotation—ArcGIS Pro | Documentation

Oracle configuration parameters—ArcGIS Pro | Documentation - search for annotation

What is annotation?—ArcMap | Documentation

FAQ: What Do the Different Fields in an Annotation Feature Class Mean?

Yes, there are changes, enhancements, bug fixes, and each ArcGIS release might introduce some change to the annotation fields.

Therefore always keep your ArcSDE Geodatabase Repository upgraded with the version of ArcGIS that you are using.

Also, there is especial attention if your annotation featureclass and data was created in ArcMap and you are migrating to ArcGIS Pro.

You can use the Upgrade Dataset GP tool to upgrade your ArcMap annotation to be editable in ArcGIS Pro.  But keep in mind once you upgrade your annotation feature class to be read/write in ArcGIS Pro, it will no longer be usable in ArcMap.  You can read more about this topic here.

Client and geodatabase compatibility—ArcGIS Pro | Documentation

You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so. Geodatabases and client software are designed to work together, and if you let one get too many releases away from the other, you risk encountering problems or unexpected behavior.

This is especially true when you use a mix of client versions at your site. A newer client can create newer dataset types in the geodatabase that older clients cannot access. For enterprise geodatabases, waiting too long between geodatabase upgrades may mean you have to upgrade the underlying database more than once before you can upgrade the geodatabase.

I hope this helps.