Edit an Entity Resolution Check

Step-by-step tutorial for changing an existing Entity Resolution check: adjust the Block and Compare Fields, the composite match threshold, the distinction field, or the filter. For which values can and cannot change, see the API page's editable and immutable lists.

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 clusters still hold more than one distinction value, a new Shape Anomaly is reported with the updated clustering. 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 inconsistent clusters.

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: Edit the fields you want to change. Each field is described in the create how-to's Field reference.

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.