Latest Contributions by Bud

...I currently am having a major struggle getting views to work in a file geodatabase at all... Yeah. I've had a lot of issues with FGDB views too. I often forget that it's possible to register an FGDB view with the geodatabase; they're not registered by default. But I don't know if that solves many problems or not; I haven't tested it enough. I talk about some FGDB database view challenges in these posts: Selecting the most recent records based on unique values in another field Select maximum values in Select By Attributes (greatest n per group) I remember finding it very helpful to put the data into a mobile geodatabase and use a SQL client like DBeaver to write my SQL queries. Then, once I'd figured out the SQL, I'd export the data to an FGDB and create an FGDB database view using the SQL I'd written for the mobile geodatabase. That's clunky, but it's better than writing FGDB SQL in the Create Database View geoprocessing tool SQL parameter. ... View more

As a workaround: We can try hiding/embedding the SQL expression using Make Query Table. The SQL expression behaves like a pre-filter, applied before the join is performed, which is what we want, unlike definition queries. https://community.esri.com/t5/arcgis-pro-ideas/consistent-visible-sql-expressions-and-query/idc-p/13... But we have to be careful not to forget about that SQL expression because it isn't visible or modifiable anywhere. I find it helps to describe the SQL expression in the layer's name.  ... View more

If the join table has a definition query, the Keep all input records parameter will have no effect. Manually updating the definition query by appending or OBJECTID is null can fix this if appropriate. https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm  ... View more

If the join table has a definition query, the Keep all input records parameter will have no effect. Manually updating the definition query by appending or OBJECTID is null can fix this if appropriate. https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm  ... View more

The Join Operation parameter has three states to adjust the cardinality. The default is blank and will allow the data source to attempt a one-to-many join. The Join one to many option will work only on specific data sources that have an Object ID field. The Join one to first option will use the first match in the table, which may result in different outputs if the Object ID field is changed or the workspace the table is copied to changes. One-to-first joins are not case sensitive; one-to-many joins are case sensitive. https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-join.htm  ... View more

Disallow select by attributes on 1:M join with duplicates ... View more

Out of curiosity, does the icon change when a view gets registered with the geodatabase via the Register with Geodatabase geoprocessing tool? A set of icons for unregistered spatial and non spatial views?  A different set of icons for registered spatial and non spatial views? ... View more