Convert a batch job to attribute rules
Available with Data Reviewer license.
Legacy:
Data quality workflows and related tools based on the Reviewer workspace have been deprecated and are no longer supported. It is recommended that you migrate to ArcGIS Data Reviewer-based validation attribute rules.
Batch jobs are files that store configured data checks created using tools in ArcMap. They are deprecated and no longer supported. You can convert a batch job configuration to validation attribute rule configurations using the Export Batch Jobs to Attribute Rules tool, which is available under the Manage Quality tab in the Convert group.
Note:
This tool only supports batch job files as source data to create validation attribute rules, not constraint attribute rules.
The Export Batch Job 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 Batch Job 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 in ArcMap and point to the same data workspace that is used as a destination workspace where attribute rules will be imported.
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. If a title exceeds this limit, it is automatically shortened during conversion.
The generated
BatchJob_Summary.xmlreport file that includes a list of checks that are successfully converted to.csvfiles is overwritten every time the tool is run if you choose the same location to store the.csvfiles.Rules created using an unsupported check type or check parameter are not converted. Starting with 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
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)
XY Tolerance (Valency check)
ValencySum (Valency check)
Flow (Valency check)
Custom Table Query (Valency check)
Search Parameters (Valency check):
In Between - Including Bounds
In Between - Not Including Bounds
Not (In Between - Including Bounds)
Not (In Between - Not Including Bounds)
For the Relationship and Duplicate Geometry checks, the Validate Destination Workspace parameter in the Export Batch Job to Attribute Rules tool is required to convert rules authored in ArcMap on a subtype with the Compare Attributes option unchecked.
The following ArcMap check types are migrated to different attribute rule types with equivalent functionality:
|
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 Reviewer batch jobs to validation attribute rules:
Start ArcGIS Pro.
On the Edit tab, in the Data Reviewer group, click Manage Quality
.Click Export Batch Job to Attribute Rules
in the Convert group.The Export Batch Job to Attribute Rules pane appears.
Click Browse
for the Batch Job file parameter, and select the batch job that you want to convert.Click Browse
for the Output .csv Location parameter and browse to the folder where you want to save the .csvfiles that are generated by the tool.Click Browse
for the Validate Destination Workspace parameter and choose the workspace where the .csvfiles are imported.This is the workspace where you will import the
.csvfiles 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.csvfiles. The summary file is located where you chose to store the.csvfiles.Batch jobs without unique check titles for a given data source are renamed in the output
.csvfiles.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
.csvfiles.
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,…).
CheckTypeName—The type of check used, such as, DuplicateCheck.
InputDataSource—The primary data source being reviewed, for example, Buildings.
SecondaryDataSource—An optional additional data source, like Parcels.
Once you import the rules, you can edit them, if necessary, and run them on your data.