Issue: Related table edits are saving to Default instead of the active branch version in Experience Builder (Enterprise 11.4)
I have a feature class and a related table that were published together from a branch-versioned enterprise geodatabase.
Here's what I've verified:
- The feature class and related table both edit correctly in ArcGIS Pro.
- I tested editing in both a named branch version and Default, and both behaved as expected.
- I published the feature class and related table together as a feature service.
- I added the service to Map Viewer in our Enterprise Portal and confirmed that the related table is included.
- I then used the map in Experience Builder and added both the Edit widget and the Branch Version Management widget.
- Both widgets are configured to use the published feature service.
The problem occurs only in Experience Builder.
When editing in a named branch version:
- Feature class edits are correctly saved to the active branch version.
- Related table edits are instead being saved directly to Default.
This creates two issues:
- Users with administrative privileges can edit the related table, but those edits are only visible in Default until the branch version is reconciled and posted.
- Users with basic editing privileges are unable to successfully save edits to the related table while working in a named branch version.
I've gone through every test I can think of, and everything points to the feature service being published correctly. It appears that the issue is specific to how Experience Builder is handling the related table in conjunction with the Edit widget and Branch Version Management widget.
Has anyone encountered this behavior before, or is there an additional configuration required to have related table edits honor the active branch version in Experience Builder?
Environment:
