Error when Splitting a polyline at an existing vertice

[HanZheng]

I noticed that ever since I updated my ArcGIS Pro to 3.4, I sometimes run into error split my line feature.

With more try and error, I realize the error happens only when I am splitting at a vertex point.

In the past, I never had issue with splitting at an vertex. I wonder if this is by design or a bug?

[RobbynAbbitt]

I can confirm that on AP 3.5.2 this is still an issue.

I can only split a line if I avoid existing vertices.  

Is there any production plan that addresses this issue moving forward?

[alex_friant]

I think the temporary work around is to make sure your layer isn't being projected on the fly - make sure your map's coordinate system matches that of the data layer you are editing.

[HanZheng]

Yes I can confirm the problem still exists. On Sept 8th, I received an email update:

BUG-000172550 is currently being evaluated by ArcGIS product teams.

Description: When using the Split tool from the Modify Features pane in ArcGIS Pro 3.4, the error message, “Splitting features failed” is returned when the map and layer projections differ.

During this review process, the product teams evaluate the customer impact, level of effort, and potential implementation timelines. There is no guarantee that this change will be implemented; however, the product team actively monitors it, and you will be notified of future updates.

[EdwardXu1]

I am running into this problem now despite the the coordinate systems lining up.

I'm using ArcGIS Pro 3.6.0.

[alex_friant]

Sounds like a reason to stay away from 3.6 until they patch it.

[MJB]

Hi Edward (and everyone),

I concur with you. I came across a line that refused to split at a vertex, and the line's feature class is using the same coordinate system as the map. 

I *was* finally able to execute the split using the By Feature tab within Modify Features > Split. My line is intersected at the vertex in question by another line, so I gave this a shot and it seems to have worked. Just one caveat, I am still running Pro 3.5.2, but perhaps this will work for the newer versions.

Hopefully this helps you and everyone else who is running into this issue.