Available with ArcGIS Pro Standard and Data Reviewer licenses.
Summary
The ArcGIS Data Reviewer Unique Field Value check finds rows in feature class attribute tables and stand-alone tables that contain nonunique values in a field or a list of fields that are editable. This can include point, line, or polygon feature classes.
Supported workflows
ArcGIS Data Reviewer checks support multiple methods for implementing automated review of data. The following table identifies the supported implementation methods for this check:
| Workflow | Supported | Licensing |
|---|---|---|
Validation attribute rule | Yes (ArcGIS Pro 2.9 and ArcGIS Enterprise10.9.1 or later) | Available with ArcGIS Pro Standard and Data Reviewer license |
Constraint attribute rule | No | N/A |
Run Data Checks | Yes (ArcGIS Pro 3.5 or later) | Available with Data Reviewer license |
Overview
The Unique Field Value check identifies recurring attribute values in the defined fields. Features or rows from the input data source are returned as errors when attribute values are not unique. You can configure this check on fields with Raster or Blob data types and on editable fields; it excludes noneditable fields, such as OBJECTID, GlobalID, editor tracking fields, and fields that have been configured as Read Only.
Industry scenarios
This check can be used in the following scenarios:
- Indoor data management—Features, such as units, must contain unique identifiers to ensure that features in floor-aware maps are associated with their corresponding facility and level.
- Tax parcel management—The record name must be unique to avoid creating records with the same name in legal plans or records of survey.
Attribute Rule syntax
The following table describes the validation attribute rule parameters:
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype(s) to which the rule is applied. | Validation |
|
Attribute |
No | A query that identifies the features to which the rule is applied. | Validation |
|
Attributes to Compare |
Yes | A list of editable fields in the input data source that evaluates unique field values. | Validation |
|
Name |
Yes | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. | Validation |
|
Description |
No | A description of the error you define when a noncompliant feature is found. This information is used to provide guidance for corrective workflows. | Validation |
|
Severity |
No | The severity of the error assigned when a noncompliant feature is found. This value indicates the importance of the error relative to other errors. Values range from 1 to 5, with 1 being the highest priority and 5 being the lowest. | Validation |
|
Tags |
No | The tag property of the rule. This information is used in rule authoring and management workflows to support traceability and reporting of data quality requirements. | Validation |
Run Data Checks syntax
The following table describes the Run Data Checks parameters:
| Parameter | Required | Description |
|---|---|---|
Input Feature | Yes | The input feature layer that is evaluated by the rule. Note:You can disable a map selection or layer definition query using the toggle button that honors the selection or filter before evaluation. Layer definition queries that include a spatial clause are not supported. |
Attribute Filter | No | A query that identifies the features to which the rule is applied. |
Attributes to Compare | Yes | A list of editable fields in the input data source that evaluates unique field values. |
Name | Yes | A unique name for the rule. This information is used to support data quality requirement traceability. |
Extent | Yes |
|
Notes
- If you configure a rule with multiple fields, the error result for the feature class displays each condition separated by a semicolon.
- The Attribute and the Attributes to Compare filter parameters do not support the following field types: Big Integer, Date Only, Time Only, and Timestamp offset.