idea If join has an error, don't create a broken join in ArcGIS Pro Ideas

If join has an error, don't create a broken join

Bud — Fri, 02 Dec 2022 21:56:39 GMT

I'm creating a join from Test_FC to Test_table via a common ID field.

In Test_Table, I've accidently set the ID field's datatype to text instead of a long integer.

Not knowing about the mistake, I attempt to create a join in the attribute table of Test_FC.

But, the join fails, because the ID field in Test_Table is text, not an integer.

Failed to refresh table. Error: The value type is incompatible with the field type.

That error message is expected.

But what's not expected is: ArcGIS Pro creates a broken join that is fiddly to deal with.

The Attribute Table automatically closes -- which isn't something I'm used to seeing.
When I try to open the Attribute Table to investigate the join, I get the same error again: Failed to refresh table.
I don't see a way to delete the join from the layer Properties:

After spending some time clicking around in ArcGIS Pro, I can see that I can remove the join using the layer's right-click context menu.

And that does seem to work -- I can remove the join and open the Attribute Table again without getting the error.

But it was a bit of a journey to get there.

Alternatively, if a join has an error, then I think ArcGIS Pro should simply not create the join, instead of creating a broken join.

Thanks.

ArcGIS Pro 3.0.2

Re: If creating a join fails, simply don't create the join, instead of creating a broken join

DanPatterson — Mon, 28 Nov 2022 22:06:27 GMT

Perhaps use this to catch other errors as well before attempting a join.

Validate Join (Data Management)—ArcGIS Pro | Documentation

Re: If creating a join fails, don't create the join, instead of creating a broken join

RoseF — Tue, 29 Nov 2022 14:20:06 GMT

Sounds like a bit of a bug; I've had this happen plenty of times and I feel like ArcMap would just make the join "fail"... not try to maintain a join that is a... failure?

And definitely validate the join first, but I assume you did that and even if you DID, if you'd run the join, it would have had the same result.

Re: If join has an error, don't create a broken join

Bud — Tue, 31 Jan 2023 17:04:50 GMT

Here's an example of join that passes the "Validate Join" test, but results in a broken join:

Join to table with definition query — column name should get prefixed (SQL expression with subquery)

Re: If join has an error, don't create a broken join

Bud — Tue, 14 Feb 2023 14:33:00 GMT

Esri Canada Case #03258990: ArcGIS Pro 3.0.3 — Broken join removed but still can't open attribute table

BUG-000155830 - Failed to open Mobile geodatabase feature attribute table after applying join from a SQL queried standalone table with error: Underlying DBMS Error [ambiguous column name objectid]

Esri Canada Case #03258894: ArcGIS Pro 3.0.3 — Validate Join passes, but resulting join has error

BUG-000155819: Attribute table of joined layer in Mobile Geodatabase does not open when a definition query with a subquery is applied to the join table