AnsweredAssumed Answered

Can't select all related features in attribute table

Question asked by erkaer on Nov 29, 2018
Latest reply on Apr 29, 2019 by tar01208

Like • Show 1 Like1
Comment • 18

After upgrading to ArcGIS desktop 10.6.1 in attribute table I can't view all related objects using 'RelatedTables' button. Only one feature with highest OBJECTID is selected, although there should be multiple related records.

Does it has something to do with BUG-000109891 "Retrieving related records in an attribute table causes ArcMap memory to spike and crash."? If so what's the solution?

Identify button and window give correct results. Everything also works in ArcGIS Pro and ArcGIS Desktop 10.5.

No one else has this question

Outcomes

17 Replies

Dan_Patterson Nov 29, 2018 3:35 AM
Mark Correct
Correct Answer
apparently that bug was fixed in 10.6.1
BUG-000109891: Retrieving related records in an attribute table cau..
2 people found this helpful
Like • Show 1 Like1
Actions
mvolz47 Nov 29, 2018 7:07 AM
Mark Correct
Correct Answer
Rafal:

Can you go through the step by step process to see this behavior in ArcMap (not Pro at this point)?
Like • Show 0 Likes0
Actions
- erkaer @ mvolz47 on Dec 5, 2018 4:14 AM
  Mark Correct
  Correct Answer
  1. When I use identify feature I can see all of the related objects in the "Identify" window.
  2. When I select the same object as above in the attribute table, and want to select all related objects by "Related Tables" button, I only get one selected feature in result, insead of all related objects
  Maybe it can be set in some application options I'm not aware of.
  Same data works as expected in 10.5 and Pro. Data is stored in file geodatabase.
  Like • Show 0 Likes0
  Actions
  - mvolz47 @ erkaer on Dec 11, 2018 8:24 AM
    Mark Correct
    Correct Answer
    What fields are you using to define your relationship class? Are these fields shown in your screen-shot?
    Like • Show 0 Likes0
    Actions
    - erkaer @ mvolz47 on Dec 14, 2018 1:50 AM
      Mark Correct
      Correct Answer
      Yes they are. These fields are 'Operator_ID' and 'Obszar_ID'. I used standalone relationship table (M-N) and Table to relationship class tool.
      Like • Show 0 Likes0
      Actions
jparkhill_FHI Jan 28, 2019 7:38 AM
Mark Correct
Correct Answer
I'm wondering if this is related (no pun intended! ) to this bug:

BUG-000116614 : When more than 99 records are selected in the feature class involved in a relationship class, the related table returns an incorrect selection result.
1 person found this helpful
Like • Show 1 Like1
Actions
KRMORRIS@nps.gov_nps Apr 23, 2019 2:40 PM
Mark Correct
Correct Answer
ESRI,

I am also experiencing a similar problem with selections of related records in related tables in SDE/SQL Server since upgrading to ArcMap 10.6.1 or 10.7.0 from 10.6.0. Our schema involves a point feature class related to a table (1-M) using an integer value ('tree number') for the relationship.

Steps
(1) Open Attribute table for Hazard Tree points and run select by attributes (query Actions='Yes'). This selects 5968 Tree points.
(2) Within the attribute table, use the button to transverse to the related table called Survey. The software takes a minute to think then produces a small set of results (approximately ~2400) but not as a selected set and not colored blue and the tab for selected records is empty. In ArcMap 10.6.0, 6840 records are correctly returned. I am concerned that the "fix" to the bug described by Don Patterson above in 10.6.1 may have inadvertently introduced another bug.

Additional Information (ArcPRO select by attributes and selected records does work)
Like • Show 0 Likes0
Actions
- mvolz47 @ KRMORRIS@nps.gov_nps on Apr 24, 2019 6:58 AM
  Mark Correct
  Correct Answer
  Kevin:
  It looks like the related record selection works properly in ArcMap 10.7.0 against an Oracle SDE database. Maybe the bug you are seeing is only with a SQL Server database as you say that is the SDE database you are using in 10.7.0. Does your SQL Server version match the supported SQL Server versions for 10.6.1 or 10.7.0 (They may be different as SQL Server versions get deprecated with ArcMap version changes).
  
  Microsoft SQL Server database requirements for ArcGIS 10.7 and ArcGIS Pro 2.3—System Requirements | ArcGIS Desktop
  Like • Show 0 Likes0
  Actions
  - KRMORRIS@nps.gov_nps @ mvolz47 on Apr 24, 2019 7:24 AM
    Mark Correct
    Correct Answer
    Michael,
    Our Enterprise SDE is operating under Windows Server 2012, SQL Server 2016 with ESRI SDE Database Version (.DBO) at 10.5.1. After noticing that I couldn't "traverse" from the root feature class (fc) to the related table in ArcMap 10.6.1, I installed ArcMap 10.7.0 and it also exhibited the same unusual behavior. I experimented with removing Xtools Pro and changed the Microsoft ODBC driver versions from 17.3, to 17.2 to 17.1. I didn't go back to driver 13 as ArcMap 10.6 had no problems with Driver 17.1 on the server.
    
    FYI: The ability to "traverse" from the primary table to the related tables using tools in ArcGIS PRO V2.3.2 works fine.
    
    By downgrading my GIS to ArcMap 10.6. I have fully restored the ability to "traverse" through primary and related tables from the attribute table graphical user interface (GUI).
    Like • Show 0 Likes0
    Actions
  - KRMORRIS@nps.gov_nps @ mvolz47 on Apr 25, 2019 7:43 AM
    Mark Correct
    Correct Answer
    Michael,
    Did you try your selection with a points feature class and several thousand records with Oracle or a poly or line fc? Another respondent indicated that with SDE/SQL Server 2016, polygons feature classes work, but they do have issues with point feature classes when selecting and traversing to the related tables for a large selection set, but not with a few records.
    
    I'm in the process of opening a ticket with ESRI on this. It is likely the behavior I am experiencing is related to BUG-000116614 and not BUG-000109891 listed in the posting. i'll try to keep this posting current based on the outcome with ESRI.
    Like • Show 0 Likes0
    Actions
    - mvolz47 @ KRMORRIS@nps.gov_nps on Apr 25, 2019 8:36 AM
      Mark Correct
      Correct Answer
      Kevin:
      I was performing my test on a polyline feature class and not a point feature class. Are this thinking that this issue only occurs with a point feature class? In 10.7 I tested with a much smaller point feature class from SDE (232 points and approximately 1000 related records) and the selected related records are working as expected, so maybe the size of the feature class is a factor. The relationship is using a Long Integer field in the relate setup.
      
      Is the point feature class you are working with a point feature class or a multi-point feature class? That might make a difference or not, it would need to be tested.
      Like • Show 0 Likes0
      Actions
      - KRMORRIS@nps.gov_nps @ mvolz47 on Apr 25, 2019 8:56 AM
        Mark Correct
        Correct Answer
        Michael,
        Thanks for the feedback. You are the first to respond with a reply on polyline tests, and perhaps they are ok like another individual indicated for polygons. My feature class is a simple point feature class (fc) and not a multi-point feature class. My point fc contains 13,217 trees records related to 13,863 survey records. There is also a second 1-M relationship from the point fc to 7768 tree action reports.
        Like • Show 0 Likes0
        Actions
    - KRMORRIS@nps.gov_nps @ KRMORRIS@nps.gov_nps on Apr 25, 2019 2:43 PM
      Mark Correct
      Correct Answer
      My issue does appear to be BUG-000116614 : "When more than 99 records are selected in the feature class involved in a relationship class, the related table returns an incorrect selection result." This was confirmed with my database where when 99 selected records traversing to the related table works, but not with 101 records.
      
      My ESRI support ticket representative replied that BUG-000116614 is resolved in ArcMap 10.7.1
      1 person found this helpful
      Like • Show 1 Like1
      Actions
      - mvolz47 @ KRMORRIS@nps.gov_nps on Apr 25, 2019 2:59 PM
        Mark Correct
        Correct Answer
        Is this bug specific to a certain spatial type (eg point) or to a specific type of database (eg SQL Server)?
        Like • Show 0 Likes0
        Actions
        KRMORRIS@nps.gov_nps @ mvolz47 on Apr 25, 2019 3:03 PM
        Mark Correct
        Correct Answer
        Not sure. There was mention that it occurs in several databases (including
        SQL Server 2016 and a version of Oracle). I didn't think to ask about
        spatial types. I'll attach more information as I get it.
        Like • Show 0 Likes0
        Actions
        KKramer-esristaff @ mvolz47 on Apr 25, 2019 3:04 PM
        Mark Correct
        Correct Answer
        Michael, here is what I see from the bug notes:
        
        Desktop 10.6.1 + Oracle 11.2.0.4--Issue reproducible
        Desktop 10.3.1 +Oracle 11.2.0.4 --Issue not reproducible
        Desktop 10.6.1 +SQL Server 2016---Issue reproducible
        Desktop 10.6.1 +Oracle 11.2.0.4 ----Issue reproducible
        Desktop 10.3.1 +Oracle 11.2.0.4 ----Issue not reproducible
        Pro 2.2.4 + SQL Server 2016 ----- Issue not reproducible
        
        This is also reproducible in File Geodatabase that contains data set with related features.
        Like • Show 0 Likes0
        Actions
        mvolz47 @ KKramer-esristaff on Apr 26, 2019 11:31 AM
        Mark Correct
        Correct Answer
        So what version of ArcMap is the file gdb bug found in, as I do not see this bug in 10.7 with a polyline feature class.
        
        In addition, I am using using Oracle 12.1.0.2 in Desktop 10.7 and I do not see this bug. I guess the bug is limited to Oracle 11.2.0.4?
        Like • Show 0 Likes0
        Actions
tar01208 Apr 29, 2019 6:14 AM
Mark Correct
Correct Answer
Also please be aware that regardless of database type, feature class type, or record count there is an issue with the "show related records" button in table view in 10.6+

https://community.esri.com/message/848692-re-show-related-records-bug?commentID=848692&et=watches.email.thread#comment-8…
Like • Show 0 Likes0
Actions

Incoming Links

Re: Show Related Records Bug?

GeoNet

The Esri Community

Can't select all related features in attribute table

Outcomes

Related Content

Recommended Content

Incoming Links