Latest Contributions by Bud

Are the tables registered with an enterprise geodatabase? I ask because I had a somewhat similar problem in an Esri Supoport case with FCs that weren't registered with a geodatabase (ArcGIS Pro 3.3.0; Oracle 18c database; non-geodatabase): Esri Case #03625510 - M-enabled SDO_GEOMETRY FC not displaying in map [unregistered feature class] BUG-000163909: 3D data in an unregistered feature class with SDO_Geometry is not displayed on the map in ArcGIS Pro.  The layer didn’t display in the map, although there were rows in the attribute table. But if I made any change to the default query layer SQL, then that fixed the query layer; it would display in the map. Even putting a random comment like /* hot dog! */ in the SQL makes the layer work. What version of SQL Server? What version of ArcGIS Enterprise? What version of Pro? Is your unique ID column truly unique and without nulls? ... View more

Can you remove the file geodatabase label from this post, since it’s not a file geodatabase? File geodatabases don’t support query layers. What version of SQL Server? What version of ArcGIS Enterprise? What version of Pro? Are you sure the field you’ve chosen as the unique ID field is truly unique and doesn’t have nulls? Can you clarify what the problem is? Is the RCODE_NO value wrong in the query layer? Can you show us a screenshot of the Fields View in ArcGIS Pro for both the underlying database table and the query layer? ... View more

Linear referencing geoprocessing tools: Create Route Events and Make Route Event Layer ... View more

I think there might be an option for this in Options > Geoprocessing.  ... View more

In the meantime I've managed to get this to work using FME rather than ArcGIS Pro Out of curiosity, what can you do with joined data/queries in FME? I assume you can’t add the data into Pro, other than maybe repurposing some SQL in a Pro query layer. For example, do you export to Excel or some other format? What do you do with the export? I ask because, as mentioned above, I too have a lot of issues with tabular/joined-base in analysis in Pro: Is ArcGIS Pro the right tool for tabular/join-based analysis?  I’m wondering if I should submit an I.T. project request for software like FME. My I.T. department is under-resourced, so it would likely take them ~10 years to get such software. So I’d want to make sure it was worth it. ... View more

For my notes: The bug report was recently changed from “In Review” to “Known Limit”. Known Limit: After review by the development team, it has been determined that this issue is related to a known limitation with the software that lies outside of Esri's control. So, that means the issue cannot be fixed. ... View more

@DrewFlater I edited the idea, as you suggested. ... View more

It would also help if the Add Join geoprocessing tool could indicate why a 1:1 join is being forced, etc. Bud_0-1715914114560.png   ... View more

How did it go? ... View more

Note: The “Duplicate rows” warning at the bottom of the attribute table is only displayed if duplicate records are present in the data. This warning doesn’t necessarily indicate if the join type is #1 vs #2. It could be #2, but no 1:M records exist in the data, so the message wouldn’t be displayed in that case. So we can’t rely on that message to indicate if the join is #1 or #2. With that said, the Layer Properties —> Joins tab does indicate the type of join in the cardinality section.  Bud_0-1715883586077.png   ... View more

For our notes, BUG-000158187 is now googleable. https://www.google.com/search?q=BUG-000158187+site%3Aesri.com  ... View more