Summary
Adds a field conflict filter for a given field in a geodatabase table or feature class.
Field conflict filters can be applied to versioned tables or feature classes to prevent conflicts from being identified when the same attribute is updated in the parent and child versions. Field conflict filters only apply for reconciles in which conflicts are defined by attribute.
Usage
Field conflict filters are not supported on the following fields: ObjectID, Blob, fields that store geometry such as Shape, the Subtype field, network-related fields such as the enabled ancillary role, and weight fields or Editor Tracking fields.
When running from the tool dialog, fields that already have filters applied and unsupported fields will not be displayed.
The ArcPy function arcpy.da.ListFieldConflictFilters() can be used to identify the fields that have filters applied.
Syntax
arcpy.management.AddFieldConflictFilter(table, fields)
| Parameter | Explanation | Data Type |
table | Table or feature class containing the field or fields to be added as conflict filters. | Feature Layer; Table View |
fields [fields,...] | Field or list of fields to add as conflict filters. | Field |
Code sample
AddFieldConflictFilter example 1(Python window)
The following Python window script demonstrates how to use the AddFieldConflictFilter in immediate mode to add a single conflict filter to the phase field.
import arcpy
from arcpy import env
env.workspace = "Database Connections/airport.sde"
arcpy.AddFieldConflictFilter_management("Primary_UG", "phase")
AddFieldConflictFilter example 2(Python window)
The following Python window script demonstrates how to use the AddFieldConflictFilter in immediate mode to add conflict filters to multiple fields at once.
import arcpy
from arcpy import env
env.workspace = "Database Connections/airport.sde"
arcpy.AddFieldConflictFilter_management("Primary_UG", ["phase","material"])
Environments
Licensing information
- Basic: No
- Standard: Yes
- Advanced: Yes