Latest Contributions by Bud

Edited. It is my understanding that there are two join scenarios in Pro (via Add Join): Forced one-to-first join (1:1), even if underlying data is one-to-many. Possible reasons Pro used a one-to-first join: At least one of the tables doesn’t have an ObjectId. Or, the tables are not in the same workspace (aka the same geodatabase). Or, at least one of the tables isn’t registered with the geodatabase (not documented) Or, the user specified the join type in Add Join in Pro 3.3.0+. Choose if join will be one-to-first or 1:Many A one-to-many (1:M) join is used/allowed, but the data might not actually have any 1:M records. Possible reasons Pro used a one-to-many join: The tables have ObjectIDs, are in the same workspace, and are registered with the geodatabase. Or, the user specified the one-to-many join type in Add Join in Pro 3.3.0+ 2.a.i above would also need to apply. Idea: In the Catalog layer properties, indicate what caused the type of join to be used since it isn’t always obvious, especially when using a map made by someone else. For example, Pro 3.2.2 Will Not Do a 1:M Join   ... View more

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB: I have two standalone tables in an EGDB that are not registered with the geodatabase (Create Unregistered Table). The relationship is 1:M. If I create a join using Add Join, the resulting join will be one-to-first (1:1), not one-to-many. Whereas, if the tables were registered with the geodatabase, then the relationship would be one-to-many. Video: The docs say the requirements for 1:M joins are: Both tables need ObjectIDs, which they have since the tables were created with the Create Unregistered Table tool. Both tables need to be in the same workspace, which they are. Could Pro be enhanced to support 1:M joins on unregistered tables, query layers, and database views? ... View more

ArcGIS Pro 2.9.5; File Geodatabase: I have two standalone tables. I join them using Add Join, resulting in a 1:M join. In the attribute table, I can't sort on the join table fields; the sort options are greyed out. Whereas the input fields are sortable. Could the attribute table be enhanced so that sorting is supported on join fields when the join is 1:M? Video: For what it's worth, in 3.3.0, I don't have this problem if I specify that the join will be one-to-first in the Add Join tool. I only have this problem with one-to-many joins.  ... View more

As @AllanBenvin_yyc said in https://community.esri.com/t5/data-management-questions/move-feature-classes-out-of-feature-dataset/m-p/1472902/highlight/true#M45154: …I am also hoping for a way to be able to move, not copy layers in/out of an FDS using arcpy. All the posts I have found refer to making a copy. This isn't feasible in our situation as it plays havoc with relationship classes, domains, archives etc. In the past we had to write a little ArcMap SDK executable that would do this. Since we have things like attribute rules now this won't work. An arcpy solution would be the best.   ... View more

What's new in ArcGIS Pro 3.3 - Analysis and geoprocessing says: The geoprocessing framework uses workspace caching to improve performance when running scripts or repeated processes. This improvement applies particularly to remote data sources, such as enterprise geodatabases. How can I find out more information about that new functionality in 3.3.0? For example, will it improve performance with Route Event Layers? I ask because in my current environment (ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB; ST_GEOMETRY), route event layers are slow: Layer Caching — How does Pro know when data was last updated?   ... View more

ArcGIS Pro 3.3.0; Oracle 19c database (non-GDB); SDO_GEOMETRY: There are cases where there are issues in Pro, and the Make Query Table tool is an effective workaround: BUG-000163909: 3D data in an unregistered feature class with SDO_Geometry is not displayed on the map in ArcGIS Pro. Testing ongoing in Esri Case #03625510 - M-enabled SDO_GEOMETRY FC not displaying in map BUG-000154798: The 'Select By Attributes' tool does not select only records with specified field values added through a one-to-many join but instead selects all records with duplicate ObjectIDs. Add Join — Indicate that a definition query on join table will effectively result in an inner join Bug - Article ID:000007166 - Open Attribute Table returns no values on a geodatabase point feature class with a join and a defini... BUG-000153808 The Add Join tool does not correctly honor the definition query on the join table. BUG-000131999 Definition query not working as expected in a joined feature layer. BUG-000129607 Add Join does not correctly honor definition query on join table. BUG-000153950 In ArcGIS Pro, when adding a join, the Keep All Target Features option is not honored if the joined ... BUG-000164109 Exported output is not the same when involving definition queries and join processes. The reason Make Query Table is an effective workaround is that Query Table seems to use a different mechanism compared to normal layers and table views. For example, a Query Table has a SQL expression, but it isn't a definition query; it appears to be hidden/embedded within the layer. As a result of that different mechanism, Query Tables work in scenarios where other feature layers and table views don't. So, it is a very handy tool, but it doesn't support enterprise database tables (non-GDB). Make Query Table (Data Management) This tool accepts data from a geodatabase or an OLE DB connection. Bud_0-1715652881490.png ERROR 000837: The workspace is not the correct workspace type. Idea: Could Make Query Table be enhanced so that it supports database tables (non-GDB)? ... View more