ArcGIS Pro 3.1.2; mobile geodatabase
I have a FC joined to a standalone table. I want to sort one of the joined fields.
In the attribute table, if I right-click a joined field, the sort ascending and descending options are greyed out.
Bud_0-1686061213737.png
Could ArcGIS Pro be enhanced so that we can sort joined fields?
It looks like this is an ArcMap equivalency issue — it's possible to sort joined fields in a Oracle 18c 10.7.1 EGDB (mobile GDBs aren't supported in ArcMap).
Esri Case #03359247 - ArcGIS Pro 3.1.2 - Unable to sort joined fields
BUG-000159170 - ArcGIS Pro 3.1.2 - Unable to sort joined fields when a mobile geodatabase standalone table is joined to a mobile geodatabase feature class in a 1 to many join.
Still a bug, over a year later. What's weirder is I see Select by Attributes is selecting WRONG on joined fields. I have an Inspection Date. It's selecting stuff BEFORE a date where I have a Greater Than condition. Joins in Pro have issues. And attachments don't come through from joined fields in webmaps. For example if we want pictures in webmap popups from a related table that was joined to its point layer, for inspections of hydrants for example. These basics would be more helpful for more customers than Digital Twin/VR/GeoAI. And less development effort.
Agree.
Is your join a one-to-many join? Select By Attributes on joined data — For rows that are 1:M, all rows in the join table get selected...
Source: Is ArcGIS Pro the right tool for tabular/join-based geodatabase analysis?
Still a bug. Yes it's one to many. Anyone? Bueller?
I can sort and manually select so to do what I do it's fine but the issue with Def Query is a bigger deal. Selection is temporary for GISers. Def Query can be needed for services; since unlike Selection; it stays updated as data changes; and this bug means joined date fields.... don't work with Def Query. Kind of a big thing. Since GIS often has inspection or fieldwork data, and of course Date of work is almost always a field.
Still having this problem in 3.6.2. Error says The SQL statement was not a select statement[STATE_ID = 0]
Thankfully I can do what I need in Excel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.