Defines the split policy for related features.
When editing features and a feature is split, the split policy on the relationship class will define how the split operation handles the split feature's related items.
The relationship origin table must be a feature class and the destination must be a nonspatial table.
If the Split Policy parameter is set to Duplicate related objects, the minimum geodatabase client version will be set to ArcGIS Pro 2.6.This means you cannot use data from ArcGIS Desktop or earlier versions of ArcGIS Pro.
Every relationship class has the default split policy Default (simple) defined upon creation for simple relationship classes and the Default (composite) policy for composite relationship classes. If the split policy has been changed to Duplicate related records, you can run this tool using the Split Policy parameter's Default (simple) value to reset the split policy for simple relationship classes or the Default (composite) value to reset the split policy for composite relationship classes.
To set the Split Policy parameter to Duplicate related records, the relationship class must be Global ID based.
If the input relationship class is stored in an enterprise geodatabase, this tool must be executed as the data owner.
The relationship class on which the split policy will be set. The origin feature class must be a polyline or polygon feature class and the destination must be a nonspatial table.
Specifies the split policy to apply to the relationship class.
The updated relationship class with the split policy set.
Set the split policy for a relationship class.
import arcpy arcpy.SetRelationshipClassSplitPolicy_management("C:\\MyProject\\sdeConn.sde\\progdb.user1.ParcelsToBuildings", "DUPLICATE_RELATED_OBJECTS")
- Basic: No
- Standard: Yes
- Advanced: Yes