In ArcGIS Enterprise 11.5 with ArcGIS Pro 3.6 and Utility Network version 7, branch versions created through a published feature service are only accessible within the same service where they were originally created.
This presents a major limitation for organizations that publish multiple services referencing the same Utility Network and same enterprise geodatabase. When a new service is published—such as for updated maps, Experience Builder apps, or operational restructuring—existing branch versions do not appear in the new service, even though the versions still exist in the geodatabase and remain valid.
As a result, editors cannot continue working on their existing planning versions unless they keep using the original service, even if that service is deprecated.
Requested Enhancement
Enable branch versions to be visible, accessible, and editable across any published feature service that references the exact same Utility Network and geodatabase, regardless of which service originally created the version.
Why This Is Critical
Large customers frequently republish or reorganize services while keeping the same Utility Network.
Editors must retain access to existing versions without being tied to one specific service forever.
Current behavior complicates service maintenance and introduces operational risk.
Existing customers using ArcMap never faced this issue, because traditional versioning allowed versions to be accessed through any connection to the same geodatabase. This is a regression in usability for customers migrating from ArcMap to branch versioning.
This affects production environments
Environment
Impact Level
High – impacts UN operations, planning workflows, and migration from ArcMap to Pro.
