The Insert/Insert/Delete split model returns an error when applied to utility network (linear) feature service layers.

Workaround

To handle scenarios where attribute rules must update attributes after a split, use Arcade expression logic similar to the following:

// If a new feature is inserted, generate a new attribute value

if ($editcontext.editType == "INSERT") {

   return NextSequenceValue("sequence_name");

}

// If the feature is updated and its geometry has changed

else if ($editcontext.editType == "UPDATE" && !Equals(Geometry($originalFeature), Geometry($feature))) {

   // Approximate split detection (i.e. a general geometry update will not always be a split):

   // Sample logic that could be refined is to apply calculation only when

/// geometry changes significantly (e.g., length reduced by ~70%)

   // AND the new feature length is greater than a minimum threshold (e.g., 5 feet)

   if (Length($originalFeature) > 1.43 * Length($feature) && Length($feature) >= 5) {

       return NextSequenceValue("sequence_name");

   }

}

Steps to Reproduce