Latest Contributions by Bud

AGOL: Advanced views (join views) are a hassle since they lock the schema of the underlying feature layers.  Once the layers are rolled into a map/app, it's too much of a hassle to drop the join, make changes to the underlying layers, re-join, and repair the map/app. This idea is to create advanced views without locking underlying feature layer schemas. ... View more

Databases like SQL Server and PostgreSQL (and Oracle) support SQL expression fields right in the table, called computed columns, generated columns, virtual columns, etc. This idea is to make use of such columns by adding an SQL expression field type, right in the AGOL table/hosted feature layer. For example, AGOL > hosted feature layer > Data tab > Fields view > a read-only field > properties > SQL expression:  'SEWER-' || asset_num_integer The other fields would remain editable in ArcGIS apps, which would be ideal. SQL expressions right in the db table would perform better than other expression mechanisms like arcade or even advanced REST API views.   A related, but different, ArcGIS Pro idea: Virtual Attributes (ad hoc) ... View more

What are the rules when setting default values for AGOL hosted feature layer fields? (using the Admin REST API) For example: Use SQL Server's SQL syntax/dialect. GIS Stack Exchange: What kind of database does ArcGIS Online use to store data? GUID and number fields support expressions, but text fields don't. Idea: Allow expressions in AGOL string field > default value Here's a useful error message I got when trying to use OBJECTID+1 as the default value for an integer field: "Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted." Link Are there any other known rules? Or any other useful error messages that could be noted here?   (To Esri staff: Could the rules be added to the AGOL docs?) ... View more

AGOL hosted feature layers; Experience Builder; editor widget When copying/pasting a feature from Layer1 to Layer2, how does ExB determine what fields to match/copy? I assume it's matching fields that have exactly the same name. Where does the list of fields to copy come from? Does the list of fields come from the AGOL hosted feature layer, the web map, the web map form configuration, the layer in Experience Builder, or the list of fields in the editor widget? True field names or field aliases? I assume true field names. If fields are excluded in the editor widget, do they not get copied/pasted? What are the rules when copying/pasting a feature into a different feature layer? ... View more

Expression fields (calculated columns) in advanced views seem to be limited to joined views. They don’t work with regular view layers.  For example, concatenate “SEWER-“ text with an integer field to produce prefixed ASSET_IDs like SEWER-0000001. Documentation: ArcGIS REST APIs > Add to Definition (Feature Service) Question: Create advanced AGOL view with expression field (no joins)? Could expression functionality be added to views that don’t have a joined table? ... View more

Summary: Admin REST API > view's sublayer > Add To Definition Added an expression field via JSON It ran without errors, but I don't see the new field in the view.   Detailed Steps: I've created a AGOL view called test_layer_view on a hosted feature layer: Bud_0-1777925565968.png In the view, using the Admin REST API, I want to add a expression field as a test, calculating 1+1. I'm not using the view's top-level feature layer... Bud_1-1777925750580.png ...Instead, I'm using the sublayer: Bud_2-1777925813867.png Bud_3-1777925989310.png (Let me know if I'm using the wrong item. Although I tested with the top-level feature layer view, and had the same issue with it.)   I got some sample JSON from the ArcGIS REST APIs > Add to Definition (Feature Service) documentation: (Those docs are pretty complicated and geared towards joins, so I'm not sure how to boil the sample JSON down to just a simple expression field without a join.) { "sourceLayerFields": [ { "name": "test_expression_field", "alias": "test_expression_field", "expression": "1+1", "type": "esriFieldTypeInteger" } ] } I hit the "Add To Layer Definition" button and it ran without errors: Bud_4-1777926103950.png Bud_5-1777926148258.png But when I refresh the view's Data > Fields tab (or the Table tab), the expression field is missing. Bud_6-1777926313848.png Likewise, the expression field is missing from the sublayer's JSON definition. What am I doing wrong?   ... View more