Skip to content

Introduction to the Predicted By Check

The Predicted By check compares a field against a value your expression predicts for the same row, allowing a tolerance either side. It is the rule for a column that is supposed to follow a formula: the expression states what the value should be, and the tolerance states how far it may drift before that matters.

This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.

Next Steps

  • How It Works

    The complete reference: definition, field scope, the prediction expression, how the tolerance band works, date and time targets, NULL handling, filter behavior, and coverage.

    How It Works

  • Anomaly Reporting

    The anomaly messages the check produces, what the numbers mean, Source Records behavior, and Custom Anomaly Description.

    Anomaly Reporting

  • Examples

    Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.

    Examples

  • Best Practices

    Guidelines for writing the prediction, sizing the tolerance, and choosing between this rule and a simpler one.

    Best Practices

  • Permissions

    The team permission each action needs: view, create, edit, archive, restore, and delete.

    Permissions

  • Create a Check

    Step-by-step tutorial for creating a Predicted By check with a prediction expression and a tolerance.

    Create a Check

  • Edit a Check

    Step-by-step tutorial for changing the expression, the tolerance, or the coverage on an existing check.

    Edit a Check

  • Delete a Check

    Step-by-step tutorial for archiving a check and deleting it permanently.

    Delete a Check

  • Troubleshooting

    Common problems with tolerance sizing, NULL results, date targets, and anomaly reporting.

    Troubleshooting

  • API

    Payload shape and field notes for creating a Predicted By check programmatically.

    API

  • FAQ

    Short answers to questions about the expression, the tolerance band, NULLs, and anomaly reporting.

    FAQ