Selecting Feature automatically triggers Edit Widget

[Tiff]

My Experience Builder app contains several editable layers and other widgets such as: Edit, Table, Legend, etc. In this app, there are a few layers where if you select the feature on a map or in the table, it automatically prompts an edit in the Editor widget. I also have a few layers that when you select the feature on the map, it shows the pop-up and does not prompt an edit.

I believe this is a setting that I have configured, but I cannot find where it is. Can someone assist who is familiar with this trigger/action setting? 

In many cases I do want the editing triggered upon a selection, but for this app specifically, we do not. And since we want consistency across all the layers, I need to turn off the immediate action after selection. Thank you!

[JeffreyThompson2]

I haven't done much with the Edit Widget and haven't touched it at all for a few versions, so I could be wrong. But as I remember the default behavior is if you have an Edit Widget and a layer is editable and editing is enabled for it, selecting a feature would trigger an editing session and there is no option to control this.

[Tiff]

Hmmm that is very interesting! I created a quick test app (with another map/layer) and was able to confirm that was the default behavior. Unfortunately it looks to be the same behavior when I create a test app with the same map as my original post. The only difference is that the layer that is not prompting an edit automatically is shared to Portal, rather than as a hosted layer in AGOL. Think this could be a bug / unintended behavior? Thanks for your insight @JeffreyThompson2 

[TianWen]

The Edit widget will automatically trigger when a feature from the associated layers is selected. In your case, if selecting features from certain layers doesn’t trigger the Edit widget, please check whether those layers are configured in the widget. Providing a sample app would also be very helpful for further investigation. Thank you!

[Tiff]

Hi @TianWen, the automatic behavior you are describing is what I am seeing for all layers, except for two layers that are shared to Portal (ArcGIS Enterprise 11.3) and shared as an item to AGOL. My data is not publicly available - can we schedule a time to chat to review this issue?

Thank you!!

[mappingmike]

Hi, did you ever find a solution for this? I've got a similar scenario where I'm migrating an app over from Web AppBuilder to Experience Builder and in the app, the user:

- uses the edit widget to create a polygon and add a few attributes.

- Then they use the select widget to select the polygon.

- Then they use the print widget to print the polygon and the custom print service takes the attributes of the selected polygon and populates the print layout with these attributes. 

In WAB this worked fine, but in Experience Builder once you've created the polygon, then go to select it and print it, the print output contains the orange edit box around the polygon because selecting the polygon goes back prompting for an edit in the edit widget.

[JeffreyThompson2]

@mappingmike Since the November 2024 ArcGIS Online Update, if an Edit Widget is placed in a Widget Controller, editing will be turned off when the Edit Widget is closed. Perhaps you can use this as a workaround?

[Tiff]

I actually did not realize that Edit widget update. If that works for you @mappingmike, great!

For my app, I did have it set up in a widget controller to begin with, and what I did was I had the Feature Info widget (in widget controller) open upon selecting a feature. Then, the user would open the Edit widget to begin editing. That way, that resolved any discrepancies in behavior.