Issue with Splitting Polygons in ArcGIS Pro 3.3 When Using Branch Versioning

[ValeskaHofmann]

Description of the Problem: In ArcGIS Pro 3.3, it is no longer possible to split polygons (using the Split tool) in a service when a layer is included twice with different symbologies. In Layer A, polygons can be split, but in Layer B, polygons cannot be split (identical source, different symbology). Layer B is displayed beneath Layer A. Importantly, we are using branch versioning, so editing on the desktop is exclusively done through a service (not directly via the data source).

Error Messages: "Splitting features failed."

Steps to Reproduce:

1. Set Layer B as the only selectable and editable layer.
2. Start an edit session.
3. Select a polygon in Layer B.
4. Choose the Split tool.
5. Split the polygon using the line tool.
6. The error message "Splitting features failed" appears.

Expected Behavior: The selected polygon in Layer B should be split successfully.

Actual Behavior: The selected polygon in Layer B is not split, and the error message "Splitting features failed" is displayed.

Troubleshooting Attempts: We tested publishing the service with only Layer B (Layer A was removed). In the test service, the selected polygon in Layer B can be split without any error. However, this is not a practical solution since both layers are required in the service.

Screenshot:

[kamadoki]

If that restores the features that have null values in MyField, then that probably confirms that ESRI probably changed it to fix what they considered to be a bug. In addition, that will be your fix, but I do empathize with you that since you've been relying on your own workaround all this time for all those projects is going to take a long time to fix them all up to add the "OR MyField IS NULL", bit.

[Bud]

For what it's worth, splitting features throws errors in traditional versioning (move edits to base) when there is a unique database index on a user-defined field, such as ASSET_ID.

[ValeskaHofmann]

Hi Bud,

thanks for the tip. We are working with branch versioning.

[JMutunga]

@ValeskaHofmann Thanks for your question and reporting this behavior. 

Can I ask why it is important for your particular workflow to have two layers with the same feature class as source in your feature service rather than what we recommend here?

Do not define multiple layers for the same feature class in the map you publish as a feature service if users will be adding the feature service to ArcGIS Pro and editing it. For example, to serve the same feature class with different symbology or different definition queries applied, create separate feature services; do not include these differently configured representations of the same feature class in the same feature service.