Available with Data Reviewer license.
Legacy:
ArcMap-based Reviewer workflows will soon be deprecated. It is recommended that current users begin converting their workflows from Reviewer batch jobs to Data Reviewer attribute rules.
Batch jobs are files that store configured data checks created using tools in ArcMap. You can convert a batch job configuration to validation attribute rule configurations using the Export to Attribute Rules tool. The tool is available from the Reviewer batch job item in the Catalog pane after you add it to the map.
Note:
This tool only supports batch job files as source data to create attribute validation rules, not constraint rules.
The Export to Attribute Rules tool generates comma-separated value (.csv) files that can be imported as attribute rules. The .csv files are generated for each feature class that contains the rules referenced in the batch job.
The Export to Attribute Rules tool relies on the parameters and workspace stored in the batch job along with the destination workspace, where the .csv file is used as imported attribute rules to ensure a successful export of checks in a batch job. Defining a destination workspace for the export operation is important, as source information, such as data subtypes, are not stored in the batch job file but in a database.
Notes
Keep the following in mind when using the tool:
- Ensure that the batch job files have been validated and point to the same data workspace that is used as a destination workspace.
- Batch job checks using units of measure that are not supported in attribute rules are automatically converted to meters. You can change the unit of measure after importing the attribute rule.
- Rule titles in the batch job cannot exceed 64 characters.
- The generated BatchJob_Summary.xml report file that includes a list of checks that are successfully converted to .csv files is overwritten every time the tool is run if you choose the same location to store the .csv files.
- Rules created using an unsupported check type or check parameter are not converted. In ArcGIS Pro 3.0, unsupported checks or check parameters include the following:
Unsupported ArcMap checks Unsupported parameters in ArcMap checks - Connectivity Rules
- Custom
- Evaluate Extent
- Invalid Event
- Invalid Hole Feature
- Metadata
- Sampling
- Topology Rules
- Valency
- Merge (Geometry on Geometry check)
- Compare All Attributes (Geometry on Geometry and Table to Table Attribute checks)
- Attributes to Ignore (Geometry on Geometry and Table to Table Attribute checks)
- Check Attributes (Duplicate Geometry check)
- Unique ID (Multiple input feature or object class)
- Check For Null parameter (Regular Expression check)
- For the Relationship and Duplicate Geometry checks, the Validate Destination Workspace parameter in the Export to Attribute Rules tool is required to convert rules authored in ArcMap on a subtype with the Compare Attributes option unchecked.
The following check types are migrated to a different attribute rule if the check was renamed or new functionality was added in ArcGIS Pro:
| ArcMap check type (configuration) | Attribute rule check type |
|---|---|
Duplicate Geometry | Duplicate Feature |
Geometry on Geometry | Feature on Feature |
Invalid Geometry | Check Geometry |
Multipart Line | Evaluate Part Count |
Multipart Polygon (Only Multiple Parts) | Evaluate Part Count |
Multipart Polygon (Only Holes) | Find Polygons with Holes |
Multipart Polygon (Parts and Holes Both) | Evaluate Part Count & Find Polygons with Holes |
Polygon Overlap/Gap is Sliver (Find Gaps) | Polygon Gap is Sliver |
Polygon Overlap/Gap is Sliver (Find Overlaps) | Polygon Overlap is Sliver |
Polygon Overlap/Gap is Sliver (Find Gaps and Overlaps) | Polygon Gap is Sliver & Polygon Overlap is Sliver |
Unique ID (Single input feature/object class) | Unique Field Value |
Complete the following steps to convert a Reviewer batch job to an attribute rule:
- Start ArcGIS Pro.
- Add the Reviewer batch jobs to an ArcGIS Pro project, if necessary.
- Ensure that the batch job files are pointing to the correct source data workspace.
The source data workspace must match the schema of the destination workspace.
- In the Catalog pane, right-click the batch job to convert and click Export to Attribute Rules
.
The Export Batch Job to Attribute Rules pane appears. The Batch Job File parameter shows the batch job file you chose by default.
- Click Browse
for the Output .csv Location parameter and browse to the location where you want to save the .csv file that is generated by the tool. - Click Browse for the Validate Destination Workspace parameter and choose the workspace where the .csv files will be imported.
This is the workspace where you will import the .csv files as attribute rules.
Tip:
Defining a destination workspace for the export operation is necessary if source information (such as data subtypes) is not stored in batch job files but in a geodatabase. The source and destination schemas must match.
- Click Export.
The export operation creates a summary file (BatchJob_Summary.xml) that includes a list of checks that were successfully converted to .csv files. The summary file is located where you chose to store the .csv files.
Batch jobs with nonunique check titles for a given data source are renamed in the output .csv files.
If a warning or error occurs during export, the specific check with an issue appears in the Errors and warnings section of the tool dialog box. Valid checks are exported as attribute rules in the .csv files.
You can import the .csv files as attribute rules with the Import Attribute Rules tool or the Import Rules tool from the Attribute Rules view. Rules that do not have a Title parameter are automatically renamed upon import using the following pattern: CheckTypeName (InputDataSource, SecondaryDataSource,…). Once you import the rules, you can edit them, if necessary, and run them on your data.