Latest Contributions by Bud

In a Survey123 form, I have a map element that lets users choose the location of the survey entry: If I paste a street address into the map search textbox like "123 XYZ ST" and hit enter, it says "There were no results found..." But if I were to click the automatic result that pops up (the picklist below the textbox), then that would work. This idea is to search for an address using the Enter key.   ... View more

I have a feature with an empty geometry in an Experience Builder app. I can't see the feature in the map, but I can see it in the attribute table. When I select the feature in the attribute table, it automatically gets selected in an editor widget. Using the editor widget, I can copy/paste the feature to the same layer. However, I can't copy/paste it to a different layer. The paste buttons are greyed out. This idea is to copy/paste a geometry-less feature to a different layer. ... View more

I have two feature layers in an Experience Builder app: Review Survey Submission External Map Points Currently, the External Map Points table opens by default when I expand the attribute table. Is there a way to change that behaviour so it opens the Review Survey Submission layer instead?   Related Idea: Set default table in Experience Builder attribute table ... View more

Using the Editor widget in an Experience Builder app: When I copy a feature with an attachment and paste it, the resulting feature doesn't include the attachment. Idea: Enhance the Paste functionality to include the attachments from the source feature. Related idea: Editor Widget — When pasting a feature, allow attachment before saving ... View more

Editor widget in a column in an Experience Builder app: Sometimes when I unclick the Select button, the action of unclicking makes the button have a blue border, which makes it look like the Select function is still active, but it's not. That's unintuitive. Could the Select button be changed so that unclicking does not give the button a blue border? Video: Google Chrome Version 146.0.7680.80 (Official Build) (64-bit) ... View more

In the web map form configuration, I've defined select fields as being read-only. The read-only fields are honored in the editor widget, but not in the attribute table; all fields are editable in the attribute table. This idea is to honor read-only fields in the attribute table. ... View more

In an editor widget in Experience Builder: I have fields that are editable and fields that are uneditable. The uneditable fields are defined that way in the web map form configuration.  The editable and the uneditable fields look the same in Experience Builder. There's no way to tell what fields are uneditable except to click on the field to see if I get a cursor or not. From a colleague: "The field border even changes to blue when you click a read-only field, just like the editable fields, making it seem like you can edit the read-only field, which is misleading." Could that functionality be changed so that it's more obvious that the fields are read-only? Such as greying the fields out, but still allowing the text to be selectable. ... View more

I have two editor widgets in columns in Experience Builder : Idea: Ability to change the text "Editor" at the top of the widgets to custom text, such as the name of the layer. Related: Info about the Experince Builder "columns": Docked Widget Panes Question: Change the name of editor widget? Idea: Make widget IDs editable in Experience Builder ... View more

I have two editor widgets in columns in Experience Builder (no editor controllers used): Is there a way to change the text "Editor" at the top of the widgets to custom text, such as the name of the layer? Related info about the columns: Docked Widget Panes Related idea: Change editor widget title ... View more

I've created a Survey123 using the Survey123 wizard. Users enter new survey submissions. In Experience Builder, using the Survey123 feature layer, I want other a user to see all fields in the Editor widget and edit a STATUS field, but not edit any other fields. Is there a way to do this, while applying the field editing restrictions securely/globally, so users can't get around the restriction in the Experience Builder attribute table, or in ArcGIS Pro, or open the service in a new map and edit it? ... View more