Find information on Release 10.0.47.18 (March 2026) of Data Quality Studio for Microsoft Dynamics 365 for Finance and Supply Chain Management.
What’s new
New or changed features in Release 10.0.47.18 (March 2026) – Data Quality Studio.
1. Ignore Blank Field Option in Fuzzy Duplicate Check
A new enhancement has been introduced in Data Quality Studio to improve the flexibility of the Fuzzy Duplicate Check functionality. In the Duplicate Check setup page, when the setup type is selected as Fuzzy Duplicate Check, an additional column named Ignore Blank is now available in the Constraint grid. This column is implemented as a checkbox field and is displayed only for Fuzzy Duplicate Check configurations.
.png)
By default, the Ignore Blank option remains unchecked for all constraint entries. Users can enable this option for specific fields by selecting the checkbox for the corresponding row in the constraint grid.
When the Ignore Blank option is selected for a particular field, the application will ignore that field during duplicate weightage calculation if the value of that field is blank in the record being evaluated. This ensures that blank values do not impact the duplicate matching score for fields where blank values should not be considered during comparison.
This enhancement provides administrators with greater control over duplicate detection behavior and helps improve the accuracy of fuzzy duplicate matching by preventing blank values from influencing duplicate weightage calculations where it is not desired.
2. Introduction of “Where Used” and Copy Functionality for Duplicate Check and Dynamic Query
An enhancement has been introduced in Data Quality Studio to improve visibility and usability when working with Duplicate Checks and Dynamic Queries. Previously, even if a Duplicate Check or Dynamic Query was being used in other Data Quality Policies, users could still modify them as long as the policy was deactivated. During active development or policy configuration, this could lead to situations where a check or query was modified by another user without clear visibility of its usage or potential impact on other configurations.
.png)
To address this challenge, a new “Where Used” functionality has been introduced on both the Duplicate Check and Dynamic Query pages. When a user clicks the Where Used button, the application displays a pop-up window listing all the places where the selected Duplicate Check or Dynamic Query is currently being used. This allows users to clearly understand the dependencies and assess the potential impact before making any modifications.
.png)
In addition to this, a Copy functionality has been introduced for Duplicate Checks, allowing users to create a copy of an existing Duplicate Check configuration. This helps users make modifications without impacting the original configuration that may already be used in other policies. The Copy functionality for Dynamic Queries already existed in the application, and with this enhancement, similar capability is now available for Duplicate Checks as well.
3. Calculated Field Support in Enrichment Rules
An enhancement has been introduced in Data Quality Studio to support Calculated Fields within Enrichment Rules in Data Quality Policies. This feature enables users to define calculated values for target fields using configurable expressions, allowing dynamic data transformation and enrichment during data processing.
As part of this enhancement, a new Value Type called Calculated Field has been added to the Enrichment Rules grid. When a user selects Calculated Field as the value type for a target field, a Calculation button becomes available. Upon clicking this button, the application opens a calculation configuration pop-up where users can define the logic used to derive the target field value.
.png)
Within the calculation configuration, users can define variables that can reference fields from either the source document or the target document. After defining the variables, users can specify the calculation expression in a dedicated text box. The result of the evaluated expression will automatically be populated as the value of the target field when the rule is executed.
.png)
.png)
To assist users in validating their logic, the configuration pop-up also provides a Test Expression functionality. This allows users to test and verify the calculation before saving the rule, ensuring the expression produces the expected output.
The calculated field functionality is not limited to numeric calculations. It also supports string-based operations, enabling users to perform common string manipulations such as replace, substring, concatenate, uppercase, lowercase, and trim. This allows users to implement both numeric and text-based transformations directly within enrichment rules.
This enhancement increases the flexibility of enrichment rules by allowing users to dynamically derive target field values based on configurable expressions, improving automation and reducing the need for manual data transformations.
Bug fixes
Bug fixes in Release 10.0.47.18 (March 2026) – Data Quality Studio.
Bug Number | Title | Description |
|---|---|---|
230766 | When importing the query, exact setup is not copied from the source | This bug fix will ensure that the while exporting and import a data quality policy from one environment to another environment, if a query is being exported and imported as a part of the setup, the all the setup most be imported from the source environment including the JOIN Type and “Query Fetch Mode”. |