topic Re: Split Tool fails in Branch Versioned Feature Service (works in DEFAULT, not in named version) in ArcGIS Pro Questions

Split Tool fails in Branch Versioned Feature Service (works in DEFAULT, not in named version)

codethemap — Thu, 28 Aug 2025 16:28:40 GMT

Hello,

When using split editing tool in ArcGIS Pro 3.5 It is working for SDE.Default versioned but It failed for named versioned with Error: Splitting Line Features Failed (even owner of the service got the error). I’d like to confirm if this is a known limitation/bug or if there is a configuration change we can make.

Environment

ArcGIS Pro: 3.5
ArcGIS Enterprise: 11.5
Data: Branch versioned feature class in enterprise geodatabase
Service: Published as a web feature layer with Version Management enabled
Editing: Performed through ArcGIS Pro against the feature service

More Info on feature service:
- We have same projections for both Map and Layers in feature service.
- Supports Apply Edits With Global Ids is true on feature service rest end

Additional Details

The service contains multiple layers from the same data source (same feature class referenced more than once, with definition queries).
We have already tried:
- Disabling or removing the duplicate layers from the map during split (still fails).

Questions

Is this a known limitation/bug with branch versioning + Split in named versions?
Are there any workarounds (without republishing the service separately) that allow Split to work in a named version?

Why we need this:

Our client requires multiple layers in the same service. Republishing separate services for each layer is not an option for us.

Re: Split Tool fails in Branch Versioned Feature Service (works in DEFAULT, not in named version)

Robert_LeClair — Thu, 28 Aug 2025 16:45:30 GMT

@codethemap - sorry to hear you're experiencing this issue. I've reviewed 16 Esri Support cases with similar issues regarding the "Splitting Line Features failed" error message. One theme constant in the cases resolved is they created a brand new *.aprx and inserted a new map view to add the branch versioned data to. They then proceeded with the split workflow and reported no new issues. Try this workflow and let me know your results - we'll go from there. Thank you!

Re: Split Tool fails in Branch Versioned Feature Service (works in DEFAULT, not in named version)

Priya_Das — Fri, 29 Aug 2025 11:01:42 GMT

Hi @codethemap - Create a Temporary Map with Only One Layer
Even if you’ve removed duplicates, try creating a brand-new map with only one reference to the feature class and test the split there. This isolates any hidden layer conflicts.

Create a copy of the layer and tested the issue.

Re: Split Tool fails in Branch Versioned Feature Service (works in DEFAULT, not in named version)

codethemap — Thu, 11 Sep 2025 06:40:38 GMT

We have recreated all the layers which are failing to split in the feature service

We tried to split them, and it succeeded with named version as well.