Skip to content

Edit a Data Diff Check

Step-by-step tutorial for changing an existing Data Diff check: adjust the compared fields, the Row Identifiers, the reference container, the Comparators, or the filters. For which values can and cannot change, see the API page's editable and immutable lists.

Permission Required

You need the Author team permission on the datastore to edit an Active check, or Drafter to edit a Draft. See the Permissions page for the full matrix.

What Happens to Existing Anomalies

Saving the edit changes only the check. The anomalies it already produced are not deleted, modified, or re-evaluated at save time.

The updated rule takes effect on the next Scan of the container: run one manually or wait for the scheduled operation. Until that scan runs, the anomaly list stays exactly as it was. On that scan:

  • A new anomaly can appear. If the two sides still differ, a new Shape Anomaly is reported with the updated comparison. When Archive Duplicate Anomalies is on, a finding that matches an anomaly that is still open (same check, same fingerprint) is archived as Duplicate instead of opening a new one.
  • Old anomalies stay open. Anomalies raised under the previous configuration keep their status until you triage them, or until a Full scan with Auto Resolve resolves it because the updated rule no longer reports a difference.

Steps

Step 1: Select the source datastore from the left menu, then click the Checks tab.

Step 2: Locate the check you want to edit and click it, or open its Settings menu and select Edit . The Authored Check Details form opens.

Step 3: Change the values you need in each section of the form. Each field is described in the create how-to's Field reference.

  • Target: the Fields compared between the two sides and the Filter Clause that scopes the target.
  • Properties: the Row Identifiers, Passthrough Fields, and Diff Change Types.
  • Right Reference: the reference Datastore, Container, and Filter Clause.
  • Comparators: the Numeric, Duration, and String tolerances.
  • Ownership: the Owner and the Anomaly Assignee.
  • Metadata: the Description, Tags, and Additional Metadata.

Locked after creation

The target table or file the check runs against and the Rule Type are locked once the check is saved. To change either, delete the check and create a new one. The reference container is not locked: it can be repointed at any time.

Step 4: Click Validate to test the updated rule against the selected data without saving it. A success message confirms the rule can run on that data. If validation fails, see Troubleshooting.

Step 5: Click Update. A success message confirms that the check was updated.