ArcGIS Pro 3.2.2
Background: Add Join not keeping all target features
When joining from tables A to B, if B has a definition query such as TYPE=100, then that definition query will effectively result in an inner join in the resulting AB join.
The Add Join tool says:
The join table has a definition query which will be applied to the input after performing the join.
Add Join should warn user if join table has a definition query
That's helpful. But I wonder if it would be even more helpful to say that the definition query will effectively result in a matches-only join, even if "Keep all input records" is checked.
Result:
Users are often confused when a join table definition query excludes rows from the resulting join. Or worse, the user doesn't notice and produces incorrect results.
It's a common issue. So I'm wondering if anything more can be done to prevent it.
Related:
If the join table has a definition query, the Keep all input records parameter will have no effect. Manually updating the definition query by appending or OBJECTID is null can fix this if appropriate.
https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.