Select to view content in your preferred language

Table joins based on GUID are inconsistent!

381
1
03-07-2024 02:05 PM
Scosh
by
Emerging Contributor

Doing a table join based on a GUID field provides inconsistent results. Sometimes it just misses a couple of features. I quadruple-checked to make sure I wasn't going crazy, but it's definitely missing a join. I compared the IDs in python to make absolutely sure they were the same.

 

Anyone else have this issue? I really need to do this, and I don't feel like creating a text version of GUIDs to do the join, because I will need to recalculate the text field every time, in order to account for any new features.

 

EDIT: I realized the underlying issue is that one of the feature classes is unable to select by attribute with certain GUIDs. I'm staring at the feature, and it says it doesn't exist. The strangest thing is that if I double click the field to start editing, but don't make any changes, then the selection works. But as soon as I click Save on the edits, the selection no longer works. And I didn't even change the attribute. I just double-clicked it like I was going to change it. I'm just gonna submit this as a bug. I hate Arc.

0 Kudos
1 Reply
GeeteshSingh07
Frequent Contributor

@Scosh, we had encountered similar issue due to a bug, however, the bug is logged for duplicate Object ID.

Do you think duplicate GUID is the issue here or if this is a different issue?

https://community.esri.com/t5/arcgis-pro-questions/select-by-attributes-on-joined-data-for-rows-that...

 

0 Kudos