Batch jobs allow you to use a set of automated checks to validate your data. Batch jobs must be pre-configured with ArcGIS Data Reviewer for Desktop to be used from the Event Editor. The Reviewer Batch Job Manager supports a variety of checks, such as SQL checks, cross-table checks, and spatial checks.
- Open Event Editor and, if prompted, sign in to Portal for ArcGIS or ArcGIS Online.
- Click the Review tab.
The Review tab in the Event Editor only displays if your deployment has been configured to support ArcGIS Data Reviewer for Server.
- Click the Run Check button and select the batch job you would like to execute.
- On the Data Reviewer Batch Job widget, click the Session drop-down arrow and choose the session that will store the check results, or follow the steps below to create a new session.
- Click New Session on the Data Reviewer Batch Job widget.
- Type a new name in the Session Name text box.
- Optionally, specify the user name.
If you have configured security through Integrated Windows Authentication, the user name will be auto-populated by the user ID accessing the secure Event Editor environment.
- Click the Duplicate Filter drop-down arrow to choose a method to remove duplicate records:
- Session—Duplicate records in the same session are not written to the Reviewer table.
- Database—Duplicate records in the same database are not written to the Reviewer table.
- None—All records are written to the Reviewer table.
- By default, Store Geometry is checked, which stores the shape value associated with each record.
- Click OK to create a new session.
- Click Run to execute the batch job.
The Reviewer table displays the returned records.
- The Data Reviewer batch job will run against the enterprise geodatabase version that the Event Editor map service is configured against.
- If you invoke a batch job to execute, the job will run to completion regardless of whether the user closes the Data Reviewer Batch Job widget or closes the browser running Event Editor. At the completion of the batch job, the error results will be written to the Reviewer workspace for later use.