Lesser-known gotchas when moving to ArcGIS Pro

[Bud]

My organization is preparing to officially move/upgrade from ArcMap 10.7.1 to ArcGIS Pro 3.1.1+ (and from Enterprise 10.7.1 to 11.1).

There are lots of good videos, courses, and docs that cover migrating to Pro. They cover some of the more common gotchas like not being able to edit personal geodatabases, etc.

What are some of the lesser-known gotchas you've come across when moving to Pro? For example, joins in Pro are one-to-many, whereas joins in ArcMap were one-to-first. (Yes, there are helpful warnings about rows being duplicated due to a 1:M join in Pro, but it's still something that can catch you off guard.)

Any other gotchas?

Thanks.

[BobFolsom1]

The big one for us on the enterprise 11 is  that we are no longer  allowed to publish services from ArcMap only ArcPro but this is well documented so I am sure you know this already.

[Bud]

Some related info from Esri Case 03370551 "ArcMap 10.8.2 compatible with 11.1 Geodatabase (Oracle)?": 
[Answer: "Yes. given that you are at a supported version of Oracle for both ArcGIS client versions."]

Also to keep in mind as your users will transition to ArcGIS Pro. There are certain data types that ArcGIS Pro no longer supports worth noting so if you have end users working with both ArcGIS Pro and ArcMap. Some examples below:
- annotations in ArcMap differs from annotations in ArcGIS Pro.
- Geometric networks are read only in ArcGIS Pro
- ArcGIS Pro uses Python 3.x whereas ArcMap uses 2.x

Tools that are not available in ArcGIS Pro:
https:///pro.arcgis.com/en/pro-app/latest/tool-reference/appendices/unavailable-tools.htm

Frequently asked questions - For ArcMap Users:
https://pro.arcgis.com/en/pro-app/2.8/get-started/faq.htm#ESRI_QUESTIONANSWERS_15E94598117D40119ECAD...

Go through this document carefully to understand the changes that have been introduced starting ArcGIS Pro 3.0 - https://www.esri.com/arcgis-blog/products/arcgis-pro/announcements/get-ready-for-arcgis-pro-3-0/

[Bud]

A couple more gotchas:

• GP Tools — Ignore selection but honor definition query
• Indicate in the map that a "selection of zero records" is applied

[Bud]

Add Join not keeping all target features [due to definition query on join table]

Select By Attributes on joined data — For rows that are 1:M, all rows in the join table get selected...