I'm interacting with an existing database, created in 10.2.0 & recently upgraded to 10.6.1. It contains table entries that participate in a relationship class (M:M). I've noticed that ArcMap cant reliably "show related records" for relationship classes built pre-10.5. Has anyone else experienced this issue? Has there been a fundamental change in the structure of relationship classes in the last several versions? This is not an extended relationship class.
Parcel 100 is linked to a single owner entry. Parcel 200 is linked to 2x owner entries (1:M). The identify tool results correctly display the relationships. The relationship tools in the attribute table do not.
This looks to be a bug. I would contact Esri Tech Support so they can log this and notify the product team.
Thank You Jake, we have contacted Technical Support & the following case has been opened:
https://my.esri.com/#/support/cases/02217404
We have further demonstrated today, that the problem is not 10.6 vs 10.2. The "show related records" action is only busted in attribute table view, in forward traverse, across relationship classes using non-ObjectIDs as Primary Keys.
I can confirm having the same issue since upgrading to ArcGIS Desktop 10.6.1 from 10.6
It affects any new FGDB and Relationshipclass created in ArcCat 10.6.1
Name: rel_streetnames_streetsegments
Origin object class: CAD_GEO_ROW_DBSTN
Destination object class: StreetSegments20190214
Type: Simple
Forward Path Label: StreetSegments
Backward Path Label: StreetNames
Message propagation: None (no messages propagated)
Cardinality: 1 - M
Has attributes: No
Origin Primary Key: STREETID
Origin Foreign Key: STREETID
Selecting all street names in CAD_GEO_ROW_DBSTN, and pushing the selection through the relationshipclass, selects all StreetSegments20190214 correctly.
Selecting all StreetSegments20190214, and pushing the selection through the relationshipclass, does NOT select the correct street names in CAD_GEO_ROW_DBSTN. Only 22 of 3227 street names are selected. About 3210 should be selected. This has been going on every time I've created the relationshipclass between the FGDB featureclass and standalone table in a new FGDB since the 10.6.1 upgrade
So if the related tables in SDE 10.5.1 show the correct results, would this break if you upgraded SDE to 10.6.1 and tried viewing related records in ArcMap 10.6.1?
The problem is client side, not server side. The actual tables themselves are fine and correct, maintaining the appropriate relationships regardless of version. The data itself is safe.
If you upgrade your desktop software to v10.6.1 you will not be able to "show related" records correctly, the error is in the desktop UI.
Thank you for the great explanation Tyler.
I have also confirmed that this bug persists in the 10.7 pre-release.
Tyler:
Is there a "show related records" button you are clicking on in the attribute table view?
Or are you selecting records from the feature class and then just opening the related records table from the table view of the feature class to see this phenomenom?
In table view, with a record selected, one of the buttons at the top of table is "show related records" a little popdown appears if you have more than one relationship established for the table. This allows you to select which one you want to traverse.
I was afraid of that. Thanks, Tyler, for testing this in the 10.7 "pre-release". ESRI SHOULD GET THIS BUG TRACKED AND FIXED before the 10.7 "RELEASE CANDIDATE" ?!?
Kory:
Is this thread showing the same bug as the following thread?
https://community.esri.com/thread/225159-cant-select-all-related-features-in-attribute-table
Not necessarily, there is apparently an additional bug that I was unaware of that impacts queries of more than 99 related objects. The tests above done on record counts less than 99. I will cross post this bug over there, because it is a variable in THEIR testing that they appear to be unaware of.
Hello, we noticed in 10.7 an issue with related records. Our parcels, 1 to many, when selected, we have less records picked (when it should be more) and then when selecting the parcel table to go back, the selection changes and the parcels are not what was originally selected. Is this related to this bug? Thanks
I think this is a bug that can date back as far as the 10.3. In a previous position, I had a ticket open with esri but off the top of my head I can't remember the bug ID. I think it has something to do with what version your database was originally created, and then the upgrading of the database (and indexes) and how the tool functions. But without knowing the inner gears of how the tool works, it's a complete guess. They don't seem to be in a hurry to fix the issue. It's kind of catastrophic in my mind... how many people actually pay close attention to the returned related records? How many false assumptions and analysis have been performed?
I'm with a new organization, just upgraded to 10.6.1 from 10.2.1 and have found this error to be persistant here. I had hoped it was going to be isolated to the previous dataset. Unfortunately.... I'll be opening another support ticket.
Thanks for the response. Yeah, we were getting some crazy results returned and had thought we had corrupted our database in our latest upgrade. As of now, we are just exporting the features classes and tables out of the SQL database and joining them back up with some other software (i.e., Access, Excel, etc.) to get the information we our looking for.
Mike
There is a patch available by contacting your esri tech support team.
ArcGIS Desktop 10.6.1 Hot FixHot Fix Name: DT-1061-HF-000004889Platform: WindowsIssues addressed in this Hot Fix:BUG-000116614: The related table returns an incorrect selection result when more than 99
This is resolved at 10.7.1
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
