Latest Contributions by Bud

On the flip side, here is an issue that was a deal breaker for my I.T. department (in conjunction with other issues) when planning to upgrade From Pro 2.9.x to Pro 3.3.5 (Enterprise 11.3). BUG-000171626 Multiple relates defined in a map cannot be published to ArcGIS Enterprise 11.3 due to the error "Map contains multiple relates with the same ID." I.T. has opted to upgrade to Pro 3.4.3 (Enterprise 11.3) instead, since the issue, and other issues, are fixed in Pro 3.4.   ... View more

Idea: Contents Pane — Use symbology class/toggles to select features ... View more

Idea: Contents Pane — Use symbology class/toggles to select features ... View more

@DrewFlater  The one-to-many option is only available if the input and join tables are in the same database, since the joining happens at the database level. FYI Esri Case #03864968 - Pro 3.4.3 - 1:M option missing from Add Join > Join Operation parameter Existing bug report: BUG-000170631: Tables in mobile geodatabase cannot perform a 'Join one to many' using the Add Join tool in ArcGIS Pro. The above also applies to enterprise geodatabase feature classes. As you noted, by default, not selecting any option will result in the software attempting a one to many join. However, the option is not there for choosing.    ... View more

Related post: Stack Overflow - Why aren't rows returned in the order of insertion? ... View more

@DrewFlater Thanks for following up. If the related record with the lowest OBJECTID is not used, then what related record does get used? Is it deterministic or arbitrary? ... View more

FYI - In Pro 3.3.5 (Oracle 19c; 11.3 EGDB), the one-to-many option is missing from the Join Operation parameter. ... View more

Idea: Raster legend labels — Make raster values like elevation the default, not the color bit numbers ... View more

@JesseWickizer Thanks, makes sense. I'd wondered but couldn't put my finger on it. ... View more

Related: Use Select by Attributes to select greatest n records (FGDB) ... View more

Related: Is ArcGIS Pro the right tool for tabular geodatabase analysis? FGDB SQL is too limited to be useful to us. ... View more

The way one-to-first joins work is: Pro grabs the related record with the lowest OBJECTID. So, if a road has a couple of related events, but the event with the lowest OBJECTID is an EVENT_STATUS='INACTIVE' event, then that event will be joined, not the other EVENT_STATUS='ACTIVE' event with the larger OBJECTID. If I had an EVENT_STATUS='ACTIVE' definition query on events prior to creating the join, Pro will automatically apply that definition query to the joined roads table when I create the join. In the example above, the definition query would omit the road entirely because the joined event is INACTIVE. So, that’s what I mean when I say the definition query is performed after the join is performed. I’m looking for a way to filter the table prior to the join being performed so that only ACTIVE events are joined. I don’t want to do a one-to-many join because I want a unique list of roads. If there were a road with multiple ACTIVE events, then that would result in duplicate roads in the attribute table if the join were one-to-many. Related: Add Join — Indicate that a definition query on join table will effectively result in an inner join Add Join — Create independent definition query on join table (pre-filter) One-to-first join — Control what related record gets used ... View more