Documentation Index

Fetch the complete documentation index at: https://docs.staedean.com/llms.txt

Use this file to discover all available pages before exploring further.

Assessment processing and result storage

Prev Next

Understanding what happens during a run helps you interpret the results and plan corrective work. When an assessment runs, Business Central:

  1. Identifies the active validation rules and duplicate checks for each selected policy.

  2. Reads the records from the policy table, applying any filters you set.

  3. Evaluates each record:

    • For validation - checks any configured conditions first, then runs the rule only when those conditions are met. When a rule fails, it creates a failed result line.

    • For duplicate checks - compares records on the configured matching fields and creates a duplicate result line for each match found.

  4. Stores a result line for every failure, with the details below.

Field

Description

Assessment Run ID

Unique identifier of the run, for example AR-000123.

Policy ID

The data policy that produced the result.

Table No. / Table Caption

The entity that was checked.

Record ID

The specific record that failed.

Check Type

Validation or Duplicate.

Field(s)

The field or fields that caused the failure.

Outcome

Whether the result is an error or a warning.

Message

The message defined on the rule.

Status

Open, Accepted Deviation, or Resolved.

Execution Date/Time

When the result was generated.

When the run completes, Business Central generates a unique Assessment Run ID and confirms the submission, for example:

Note

Note or copy the Assessment Run ID so you can search for the run later in Validation History.
Example: “Data Quality Assessment has been submitted successfully. Assessment Run ID: AR-000123. Use this Assessment Run ID to track progress and review results in Validation History.”