Data Quality Studio for D365 BC helps organizations ensure that master data meets defined quality standards before it is saved. This guide explains how to configure Data Quality Studio for D365 BC and covers the two main capabilities: Validation Rules and Duplicate Checks.
What is Data Quality Studio for Microsoft Dynamics 365 Business Central?
Data Quality Studio for D365 BC is an extension built by STAEDEAN that brings structured data Quality Management to your D365 BC environment. It allows data quality administrators to define rules that are automatically evaluated when users create or update master data records.
When a rule is violated, the system responds immediately either by showing an error that prevents the record from being saved, or by showing a warning that the user must acknowledge before continuing. This ensures that data quality issues are caught at the point of entry, rather than discovered later during reporting or integration.
Data Quality Studio for D365 BC is based on the same data quality concepts as STAEDEAN Data Quality Studio for , adapted for the D365 BC platform.
Supported Master Data
Data Quality Studio for D365 BC is designed and validated for the following master data tables:
Entity | D365 BC Table |
|---|---|
Customer | 18 |
Vendor | 23 |
Contact | 5050 |
Note
The design is scalable and can be extended to additional tables in future phases. However, currently only the three entities listed above are officially supported.
Main Capabilities
Data Quality Studio for D365 BC provides two main capabilities:
1. Validation Rules
Define rules that check whether a field value meets a defined standard. You can make a field mandatory, require it to be blank, validate it against a regex pattern (such as an email format), or check that it falls within a numeric range. Rules can also be conditional and apply only when specific filter criteria are met on the record.
2. Duplicate Checks
Define checks that detect whether a record being created or updated already exists in the system based on one or more matching fields. When a duplicate is detected, the system either shows a warning or prevents the record from being saved, depending on how the rule is configured.
Who Should Use This Guide
This guide is intended for:
Data Quality Administrators - Responsible for setting up and maintaining Data Quality Studio policies, rules, and checks
Functional Consultants / Implementation Partners - Configuring Data Quality Studio as part of a D365 BC implementation
Project Managers - Looking for a high-level overview of the configuration process.