Manage data quality policy changes

With data quality policy change management, you can manage changes on your data quality policies and all related components. This includes all data quality policy details and components, like configurable lookups, web service configurations, data patterns, or duplicate checks.

Activate change management

Activate data quality policy change management in the Data quality studio parameters.

Change sets

Changes to data quality policy details and related components are stored by data quality policy change set. Each data quality policy change set is stored as a file in the file storage folder as defined in the Data quality studio parameters.

Synchronize data quality policies

You can use data quality policy change management to synchronize data quality policies between several D365 F&SCM environments. For change management, the file storage folder, as defined in the Data quality studio parameters, must be the same for all environments between which data quality policy change sets must be synchronized. So, the change set files are stored centrally and can be accessed by all applicable environments.

• In Data Quality Studio, if change management is active, you:

• Manage changes on data quality policy level only, including all data quality policy components and settings.

• Must check out a data quality policy to make changes to the data quality policy or its components.

• Must check in a data quality policy to make changes generally available for other environments.

• Can restore a data quality policy change set or get the latest data quality policy change set.

Example

This picture shows an example of a typical environment setup. For each environment, data quality policy change management is active, using the same Azure Storage Account and folder to store data quality policy change set files. In this case, the data quality policy is checked out on the Development environment, changes are made, and the data quality policy is checked in. Because the changes are required in the Acceptance environment, Get latest is done here.

Change management scenarios

You can use data quality policy change management, for example, for these scenarios:

• Data quality policy changes: A change to a data quality policy component in an environment can be easily applied to other environments.

• Issue solving: During testing, you can find and solve an issue in a data quality policy component in one environment. The solution to the issue can be easily applied to other environments.

• Updates in the test environment: In a test environment, data quality policy components are often changed. Using data quality policy change sets, you make sure that changes are saved, and you can always restore a previous data quality policy change set.

Note

Data quality policy versions and data quality policy change sets are separate but related entities.

A version represents a specific state of a data quality policy. A change set tracks and applies changes made to that policy.

For example:

To activate a specific data quality policy version:

1. Check out the data quality policy.

2. Activate the desired version.

3. Check in the data quality policy to apply the active version through a change set.

The change set records the version activation as part of the data quality policy’s tracked changes.

Flow diagram