I’m working on an Experience Builder app with multiple editable point layers. I am on Enterprise 11.5 (which I believe corresponds to ExB 1.17).
In my web map:
- One layer is set to display on initialization
- The remaining layers are turned off by default
I’m seeing different behavior depending on how the Edit widget mode is configured.
Behavior in "Attribute Only" mode:
- I’ve configured multiple layers as editable in the widget.
- When I select a feature (from any configured layer), the Edit widget immediately loads that specific feature’s attributes in the panel.
- It does not show the default edit screen (the one that prompts you to select or create features).
This behavior is ideal for my workflow.
Behavior in "Interact with Map Widget" mode:
I need to use this mode because my point features have related records, which are only accessible in this mode.
However, the behavior changes:
- Only layers that are visible on initialization will properly populate the Edit widget when selected.
- If I turn on a layer that was initially off:
- Selecting a feature does not update the Edit widget
- The widget stays on the main edit menu (Select / Create)
- To edit that feature, I have to:
- Use the Edit widget’s Select tool
- Select the feature again manually
What I’m Trying to Achieve
I want the Edit widget (in "Interact with Map Widget" mode) to:
- Automatically switch to the selected feature
- Regardless of whether the layer was initially visible or turned on later
- Similar to how "Attribute Only" mode behaves
This is important because:
- Users need to quickly switch between features
- Related records must be visible and editable alongside the feature
Is there a way to make the Edit widget respond to feature selections from layers that were not visible on initialization, or configure it so it behaves more like "Attribute Only" mode while still supporting related records? Or is there a way to show related records while in "Attribute Only" mode? I am open to any other options as well if anyone else has run into this.
