Latest Contributions by Bud

Thanks @rsun_TQB. Will this work for a feature that has multiple attachments? ... View more

@NicoleJohnson Thanks. Esri, feel free to mark this idea as "Already Offered". ... View more

@JonathanMcD Where in the AGOL > Visualizations tab would you set the view's field order? In the popup properties > Fields List?     ... View more

From a comment in Add GUID field to existing AGOL Survey123 feature layer — Field not auto-populating? GUID fields don't autopopulate, they default to null.  They're typically up to the application or an editor to set. You could make a hidden field in your S123 form for the question and use the uuid() function to populate it. Alternatively, you can use the Admin REST API to create the field with a NEWID() default value, with the Add to Definition endpoint of the layer.  It may be possible to update an existing field's default value with this as well, but I haven't tried it.  This will make the field autopopulate with a new value in the same way that Global IDs are autopopulated: { "fields": [ { "name" : "MyID", "type" : "esriFieldTypeGUID", "alias" : "My ID", "sqlType" : "sqlTypeOther", "length" : 38, "nullable" : false, "editable" : false, "domain" : null, "defaultValue" : "NEWID() WITH VALUES" } ] }   ... View more

@JonathanMcD, you might like @MobiusSnake’s comment in Add GUID field to existing AGOL Survey123 feature layer — Field not auto-populating? GUID fields don't autopopulate, they default to null.  They're typically up to the application or an editor to set. You could make a hidden field in your S123 form for the question and use the uuid() function to populate it. Alternatively, you can use the Admin REST API to create the field with a NEWID() default value, with the Add to Definition endpoint of the layer.  It may be possible to update an existing field's default value with this as well, but I haven't tried it.  This will make the field autopopulate with a new value in the same way that Global IDs are autopopulated: { "fields": [ { "name" : "MyID", "type" : "esriFieldTypeGUID", "alias" : "My ID", "sqlType" : "sqlTypeOther", "length" : 38, "nullable" : false, "editable" : false, "domain" : null, "defaultValue" : "NEWID() WITH VALUES" } ] }   ... View more

@Shen_Zhang Thanks for your reply. The Review Survey Submission layer has always been the first layer in the web map Contents, so I'm not sure why it wasn't being honored in the Experience Builder attribute table.   I also can't get it to work in the table widget custom properties in Experience Builder. Review Survey Submission has always been first in the list, but isn't being honoured either.  I thought for a second I got it working by removing External Map Points from the table, saving, re-adding it, and saving. But now I can't reproduce it, so maybe I was mistaken. I wonder if something isn't working quite right with this functionality. ... View more

I wondered if I could set up an Arcade expression in the layer2 ORIGINAL_ID field, using form configuration in the web map. The expression would grab the OBJECTID from layer1. But I don't know how that would work, since the expression wouldn't know what layer1 feature to grab the OBJECTID from; there's no tabular relationship. I guess there is a spatial relationship, since the two points have the same location, but that seems pretty clunky. And that wouldn't work for geometry-less features or records in a non-spatial table. I don't have any experience with Arcade expressions in form configuration. So I'm just guessing. ... View more

@Katie_Clark It's kind of a headscratcher why this functionality doesn't already exist. Stable unique IDs are data management 101. A must-have. ... View more

@Neal_t_k  Thanks for the info about Connect! I don't have experience with it. I will look into it. Also, there should be GlobalID in your Survey123 layer (layer1) already that you could copy to layer 2 I've wondered about this too. The ExB copy/paste functionality seems to copy/paste into fields that have exactly the same field name. However, as far as I can tell, the destination feature gets a different/new GlobalID, not the GlobalID from the source feature. So I think I'm out of luck here. I'm not aware of a way to "field map" the source GlobalID to a custom destination field like ORIGINAL_GLOBALID.  Experience Builder Idea: Field mapping for copying/pasting features using Editor widget ... View more

Related ArcGIS Online Idea: Auto-incrementing integer field (at AGOL feature layer level) ... View more

I've submitted an idea: Auto-incrementing integer field (at AGOL feature layer level) ... View more