Configuration

The following sections walk through every configuration step required to set up Data Quality Studio in D365 BC. Complete them in the order they appear.

Configuration overivew

This section gives a high-level overview of the complete Data Quality Studio configuration flow and describes the key limitations.

Configuration Flow

To make Data Quality Studio for D365 BC operational, complete the following steps in order:

1. Enable Data Quality Studio globally - Turn on the Data Quality Check toggle in the Data Quality Setup page

2. Verify number series - Confirm that number series are assigned for validation conditions, duplicate conditions, and duplicate checks

3. Create a Data Quality Policy - Create one policy per master data table (Customer, Vendor, or Contact)

4. Configure policy version - A Version 1 is created automatically; activate it when configuration is complete

5. Configure validation rules - Define field-level rules within the policy version

6. Configure data patterns (if needed) - Create reusable regex or range expression patterns before selecting them in validation rules

7. Configure duplicate checks - Define the matching logic (fields, check type) as a reusable duplicate check definition

8. Link duplicate checks to the policy - Attach the duplicate check to the policy version and set the outcome behaviour

9. Activate the policy version - Flip the Active toggle on the version to put it into effect

Note
Configure data patterns and Configure duplicate checks can be done in Anywhere Mobility Solutions order or in parallel. All other steps follow the sequence listed above.

Key Concepts

Policy
A Data Quality Studio is the container that links a master data table to a set of rules. You create one policy per table. Each policy can have multiple versions, but only one version can be active at a time.

Policy Version
A version holds the validation rules and duplicate check rules. Versions have three states:

• Draft - The working copy, editable, not yet evaluated

• Active - The enforced version; rules fire during data entry

• Inactive - A previous version that has been superseded

Validation Rule
A rule that checks a specific field value against a defined criterion (mandatory, blank, data pattern, range expression). Can be conditional.

Validation Pattern
A reusable definition of the format or range that a field value must match. Created in the Validation Patterns Setup page and referenced by validation rules.

Duplicate Check
A reusable definition that specifies which table and which fields to compare when detecting duplicate records. Attached to a policy version and given an outcome (warning or error).

Data Condition
A filter attached to a validation rule or duplicate check rule that restricts when the rule fires. If the condition is not met, the rule is skipped.