When importing data from geopackage or sqlite any field defined as Integer in the DDL gets cast to BigInteger instead of (Long) Integer. This is a new incompatible behaviour since BigIntegers were included (ArcPro 3.2?). There are several tools that do not work with BigIntegers such as RelationshipClasses.
It would be helpful if there was a switch to turn off this unwelcome enhancement. There is a switch in Options/Map and Scene - but it doesn't work.
The only way to fix the problem is to define a FieldMapping on every copy operation and there are many of these that do not have FieldMapping as a parameter.
If the field is readonly such as OBJECTID then it cannot be changed at all. I see another user has used FME to fix this.
This is like a reverse single precision / double precision incompatibility!
Maybe a switch somewhere in the settings or the environment settings to retrofit a fix?
