|
POST
|
Thanks @rsun_TQB. Will this work for a feature that has multiple attachments?
... View more
3 weeks ago
|
0
|
0
|
143
|
|
IDEA
|
@NicoleJohnson Thanks. Esri, feel free to mark this idea as "Already Offered".
... View more
3 weeks ago
|
0
|
0
|
222
|
|
IDEA
|
@JonathanMcD Where in the AGOL > Visualizations tab would you set the view's field order? In the popup properties > Fields List?
... View more
3 weeks ago
|
0
|
0
|
160
|
|
POST
|
Can Power Automate and webhooks be used for the following in AGOL? When a feature with multiple attachments is created in a Survey123 feature layer, copy the feature to a different feature layer, including copying the multiple attachments. (Event-driven webhook, not on a schedule.)
... View more
4 weeks ago
|
0
|
3
|
307
|
|
POST
|
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
4 weeks ago
|
0
|
0
|
424
|
|
IDEA
|
@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
4 weeks ago
|
0
|
0
|
474
|
|
POST
|
I have a Survey123 feature layer that was created using the Survey123 wizard. I need a custom auto-populated unique ID field, so I've added a GUID field using AGOL > Data > Fields. This is the resulting field: Problem: When I create new features in an Experience Builder app using the Editor widget, the new GUID field is not being populated. Why isn't it being populated? Use Case: Auto-populate unique ID field in hosted feature layer (common ID between copy/pasted features in ExB) I need a custom unique ID field so the values will be copy/pasted into a new feature in a different feature layer. The ExB editor widget matches fields in the source layer (the Survey123 layer) with fields in the destination layer, where the field names are an exact match. I can't use the OOTB OBJECTID or GlobalID fields from the source layer, because the destination feature will get new values in those fields, not the values from the source feature.
... View more
4 weeks ago
|
0
|
19
|
1298
|
|
POST
|
@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
4 weeks ago
|
0
|
0
|
120
|
|
IDEA
|
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
4 weeks ago
|
0
|
0
|
166
|
|
IDEA
|
@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
4 weeks ago
|
0
|
0
|
533
|
|
POST
|
@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
4 weeks ago
|
0
|
0
|
446
|
|
IDEA
|
Related ArcGIS Online Idea: Auto-incrementing integer field (at AGOL feature layer level)
... View more
4 weeks ago
|
0
|
0
|
348
|
|
POST
|
I've submitted an idea: Auto-incrementing integer field (at AGOL feature layer level)
... View more
4 weeks ago
|
0
|
0
|
459
|
|
IDEA
|
This idea is to create an auto-incrementing integer field using the AGOL UI. The mechanism would be at the AGOL feature layer level, not at the app level, so it can be used globally. The OBJECTID field isn't suitable because it can't be used everywhere, such as for copy/pasting features in the Experience Builder editor widget. Further, it's generally considered unwise to rely on OBJECTIDs. Related AGOL Question: Auto-populate unique ID field in hosted feature layer (common ID between copy/pasted features in ExB)
... View more
4 weeks ago
|
4
|
4
|
591
|
|
IDEA
|
I'm copying/pasting features from layer1 to layer2 using the Editor widget. I want to set up field mapping so that layer1 OBJECTIDs would be copied to a layer2 ORIGINAL_ID field. Use Case: I want there to be a common ID between the two features so I can know what the layer1 source feature was for the layer2 destination feature. Idea: Could field mapping functionality be added to the Experience Builder Editor widget for copy/pasting features? Related AGOL Question: Auto-populate unique ID field in hosted feature layer (common ID between copy/pasted features in ExB)
... View more
4 weeks ago
|
0
|
1
|
209
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 1 | 03-19-2026 09:29 AM | |
| 2 | 2 weeks ago | |
| 1 | 2 weeks ago |