I'm trying to build an Experience Builder app in ArcGIS Enterprise 11.5 for editing a branch-versioned Utility Network. The goal is to allow users to select Water UN and Sewer UN features on a map and edit their attributes only, while having those edits go to a specific named branch version rather than DEFAULT. Geometry editing needs to remain enabled on the underlying feature services because administrators still need to edit geometry in ArcGIS Pro.
I've tried using the Branch Version Management widget with the Water UN and Sewer UN feature services added directly to the Experience Builder app. The Version Management widget successfully allows me to switch those feature services between branch versions. However, those directly added feature services are not the interactive layers displayed in the Map widget. The Map widget uses a web map, so I put the Water UN and Sewer UN feature layers into a web map and added that web map to the Map widget. I can use Map Viewer to set the layers in that web map to a specific branch version, and the map displays that version correctly. However, when I edit a feature through Experience Builder, the edit is still written to DEFAULT rather than the branch version displayed in the web map.
I also tried configuring the Edit widget as "Attribute Only" and selecting the Water UN layer from inside the web map. The feature can be selected and edited, but the edit still goes to DEFAULT. Adding the feature service directly to the Edit widget allows the Version Management widget to control its version, but then that data source is not the interactive layer displayed in the Map widget. This makes me question the purpose of using the Version Management widget in this configuration: it can switch the version of a feature service that users cannot directly interact with on the map, while the layer they actually select and edit is still using DEFAULT. Is there a supported workflow in Enterprise 11.5 that allows a Map widget to display a branch version and have an Attribute Only Edit widget edit that same branch version, while leaving geometry editing enabled on the underlying service for ArcGIS Pro administrators?
