Available with Data Reviewer license.
Summary
The Table to Table Attribute check finds features or rows that contain attribute values that meet a relationship you define and compares them to values in another feature class or stand-alone table. This can include comparing string values that match or do not match, numeric values that are greater than or less than those in a related field, and dates that are not equal.
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.7 and ArcGIS Enterprise10.9 or later) | Available with ArcGIS Pro Standard and Data Reviewer license | |
Constraint attribute rule | No | Available with ArcGIS Pro Standard and Data Reviewer license | |
Run Data Checks | Yes (ArcGIS Pro 3.4 or later) | Available with Data Reviewer license | |
Overview
The Table to Table Attribute check identifies attribute values that meet a relationship you define and compares them to values in another data source. This can include a comparison of values stored in a feature class to those stored in a stand-alone table, values stored in a feature class to those stored in another feature class, or values stored in a stand-alone table to those stored in another stand-alone table. Features or rows from the input data source are returned as errors when attribute values match the defined relationship.
Industry scenarios
This check can be used in the following scenarios:
- In address management, the names of road centerline features should match those stored in a master street index, such as the Master Road Name table.
- In tax parcel management, the legal start date of a parcel feature should match the legal date a plan or record of survey was recorded.
Attribute Rule syntax
| Parameter | Required | Description | Workflow |
|---|---|---|---|
|
Subtype |
No | The subtype to which the rule is applied. | Validation |
|
Attribute |
No | A query that identifies the features to which the rule is applied. | Validation |
|
Features to Compare |
Yes | Input features or rows are returned as errors based on their relationship to the features or rows from this data source. Valid inputs are point, polyline, polygon, and stand-alone table data sources. | Validation |
Filter | No | A query that identifies the features to include in the rule, from the data source specified in the Features to Compare parameter. | Validation |
|
Attribute Relationship |
Yes | The attribute value comparison between features or rows from the input data source and the data source of the Features/Rows to Compare parameter. | Validation |
|
Invert Relationship |
No | After the relationship is evaluated, this option determines whether the result should be used as is or inverted. For example, this option can be used to identify attribute values that do not match values from the data source of the Features/Rows to Compare parameter.
| 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
| Parameter | Required | Description |
|---|---|---|
Input Feature | Yes | The input feature layer that is evaluated by the rule. |
Attribute | No | A query that identifies the features to which the rule is applied. |
Features to Compare | Yes | Input features or rows are returned as errors based on their relationship to the features or rows from this data source. Valid inputs are point, polyline, polygon, and stand-alone table data sources. |
Filter | No | A query that identifies the features to include in the rule, from the data source specified in the Features to Compare parameter. |
Attribute Relationship | Yes | The attribute value comparison between features or rows from the input data source and the data source of the Features/Rows to Compare parameter. |
Invert Relationship | No | After the relationship is evaluated, this option determines whether the result should be used as is or inverted. For example, this option can be used to identify attribute values that do not match values from the data source of the Features/Rows to Compare parameter.
|
Name | No | A unique name for the rule. This information is used to support data quality requirement traceability, automated reporting, and corrective workflows. |
Visible Extent | No | Evaluate the visible extent of the map. |
Full Extent | No | Evaluate the full extent of the data. |
Notes
Keep the following in mind when using the check:
- Comparisons defined in the Attribute Relationship parameter that only include the is not equal to operator must use the Invert Relationship parameter and the is equal to operator instead. For example, use the following configuration to identify attribute values in the input data source that do not exist in the data source of the Features/Rows to Compare parameter:
Parameter Input Attribute Relationship
<Input.FieldToCompare> is equal to <Features/RowsToCompare.FieldToCompare>
Invert Relationship
Checked
- This check supports the comparison of values stored in text, numeric, and date field types. It also supports the comparison of values in text fields with those stored in globally unique identifiers (GUIDs) and Global ID field types, or the ObjectID field.
- The Validation Status attribute values of both the input features and the data sources included in the Features/Rows to Compare parameter are ignored during evaluation. For example, input features with a validation status of 0 (No calculation required, no validation required, no error), 1 (No calculation required, no validation required, has error(s)), 4 (Calculation required, no validation required, no error), or 5 (Calculation required, no validation required, has error(s)) are still included during rule evaluation.
- Data sources for the Features/Rows to Compare parameter must include a global ID field.
- Include the data source for the Features/Rows to Compare parameter when creating map or project packages, and sharing web layers with the Validation capability enabled.
- The Attribute filter parameter is limited to comparison (=, <>, >, <, >=, and <=) and logical (AND/OR, IN/NOT IN, LIKE/NOT LIKE, and IS NULL) operators.
- The Attribute and the Attribute Relationship filter parameters do not support the following field types: Big Integer, Date Only, Time Only, and Timestamp Offset.