ArcGIS Pro 3.3.5; Oracle 19c 11.3 EGDB; standalone tables:
One-to-first joins are supposed to use the related record that has the smallest OBJECTID.
Add Join
The Join Operation parameter has three states to adjust the cardinality. The default is no value and will allow the data source to attempt a one-to-many join. The Join one to many option will work only on specific data sources that have an Object ID field. The Join one to first option will use the first match in the table, which may result in different outputs if the Object ID field is changed or the workspace the table is copied to changes. One-to-first joins are not case sensitive; one-to-many joins are case sensitive. If the joined table does have an Object ID, the first match will be the record with the lowest Object ID.
In ArcGIS Pro 3.3.5, that seems to apply to file geodatabases, but not to Oracle enterprise geodatabases. Pro seems to be grabbing a different related record; it isn’t grabbing the lowest OBJECTID.
My I.T. department is currently in the process of upgrading us from Pro 2.9.5 to 3.3.5 (10.7.1 EGDB to 11.3 EGDB). Are there any patch levels of 3.3.x that don't have this issue? Maybe we could pivot to a different patch level of 3.3.x.
I ask because we were really looking forward to using the new one-to-first join functionality as a way of working around some of the issues we have in Pro that are related to one-to-many joins. It would be disheartening if we couldn't use one-to-first joins, since EGDB tabular analysis is a huge part of our business.
