Flows

You can run a data quality assessment project to examine the quality of existing data.

You can do a data quality assessment, for example, if you:

• Have implemented a change in the Data quality studio configuration and want to make sure existing data is in line with this change.
• Have imported data without applying data quality policies.
• Want to periodically check the quality level of your data.

As a data owner, you can review and process data quality assessment results. A data owner can be a:

• General data owner who can review and process quality assessment results for all companies.
• Company-specific data owner who can review and process quality assessment results only for an assigned company.

For each failed validation rule or duplicate check rule, a separate entry is created in the Quality assessment exceptions log.

The options you must review and solve quality assessment results depend on the origin of the found issues:

• Validation rule not met.
• Duplicate check finds possible duplicate records.

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 data quality policy change management in the Data quality studio parameters.

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.

• 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.

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.

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.

Data quality policy change management offers several advanced options. For example, to solve issues related to data quality policy change sets.

For each action rule, you can set up conditions. The action rule is only applied if the conditions are met.

Use action rules to set field values in D365 F&SCM.
To set a field value, you can use several action types. This topic explains how to set up an action rule of type Custom.

Use action rules to set field values in D365 F&SCM.
To set a field value, you can use several action types. This topic explains how to set up an action rule of type Data query.

Use action rules to set field values in D365 F&SCM.

Use action rules to set field values in D365 F&SCM.

Use action rules to set field values in a target field in D365 F&SCM.
To fill in data, you can use these action types:

• Fixed value: Sets a pre-defined fixed value in the target field.
• Data query: Uses an inquiry or dynamic query to find a value and set it in the target field.
• Transformation list: Uses a transformation list to find a value and set it in the target field.
• Number sequence: Uses a number sequence to set a value in the target field.
• Web service: Uses a web service to get a field value from another internal or external source and set it in the target field.
• Custom: Uses a custom action class to set the target field value.

For each action rule, you can set up conditions to define the data to which the rule applies.

You can set up a configurable lookup to define the possible options in a field.

You can define the possible options for a configurable lookup in these ways:

• User defined list: Set up the desired options manually.
• Dynamic query: Apply a dynamic query to define the desired options.
• Web service: Use a web service to get the desired options.

To apply a configurable lookup, set up a validation rule of type Configurable lookup. You can use a configurable lookup on several validation rules.

This topic explains how to set up a configurable lookup.

You can use duplicate check rules to check if data doesn't already exist in D365 F&SCM.

Before you can set up a duplicate check rule, set up the duplicate check to be applied.

You can apply these types of duplicate checks:

• Basic matching: Checks which combination of table fields has duplicate values. So, the combination of field values must be unique in the table.
• Fuzzy matching: Checks for duplicates applying fuzzy logic. A fuzzy duplicate check compares values from several fields. Based on the comparison, a duplicate score is calculated.

For each duplicate check rule, you can set up conditions. The duplicate check rule is only applied if the conditions are met.

Use a duplicate check rule to check if the data doesn't already exist in D365 F&SCM.

Use a dynamic query to find one or more records in the database. The found records are the input for further processing.

You can use a dynamic query on:

• An enrichment rule of type Data query.
• An action rule of type Data query.
• A condition that is applied to a validation rule, duplicate check rule, or action rule.
• A configurable lookup of type Dynamic query. You can apply the configurable lookup on a validation rule of type Configurable lookup.

To define a query range, you can use a function.

For each enrichment rule, you can set up conditions. The enrichment rule is only applied if the conditions are met.

Use enrichment rules to set field values in D365 F&SCM.

To set a field value, you can use several value types. This topic explains how to set up an enrichment rule line of type Custom.

Use a custom enrichment rule line to set a field value using a custom class.

Before you can set up a custom enrichment rule line, ensure that the custom class is developed.

Use enrichment rules to set field values in D365 F&SCM.
To set a field value, you can use several value types. This topic explains how to set up an enrichment rule line of type Data query.

Use enrichment rules to set field values and behavior in D365 F&SCM.

To set a field value or behavior, you can use several value types. This topic explains how to set up an enrichment rule line of type Enable/Disable.

Use an Enable/Disable enrichment rule line to disable or enable a field based on the value of another field.

Usually, for an enrichment rule of type Enable/Disable, you apply:

• The 'Source field modified' event.
• A condition to define for which value of another a field is enabled or disabled.

Note:

• For a specific field, you can only set up one enrichment rule line for each enrichment rule.
• If you set up an enrichment rule with a line to disable a field, you must also set up an enrichment rule with a line to enable the field.

Example:

This example explains how you can apply an enrichment rule line of type Enable/Disable. As an example, the credit rating of a customer is used.

For this example, three enrichment rules are required, each with an enrichment rule line on the Credit limit field:

Use enrichment rules to set field values in D365 F&SCM.

To set a field value, you can use several value types. This topic explains how to set up an enrichment rule line of type Fixed value.

Use a fixed value enrichment rule line to set a pre-defined fixed value in the target field of the enrichment rule line.

Use enrichment rules to set field values in D365 F&SCM.

To set a field value, you can use several value types. This topic explains how to set up an enrichment rule line of type Number sequence.

Use a number sequence enrichment rule line to set the value of the target field of the enrichment rule line based on a number sequence.

Use enrichment rules to set field values in D365 F&SCM.

Use enrichment rules to set field values in D365 F&SCM.

Use enrichment rules to set field values in a target field in D365 F&SCM.
To fill in data, you can use these enrichment types:

• Fixed value: Sets a pre-defined fixed value in the target field.
• Data query: Uses an inquiry or dynamic query to find a value and set it in the target field.
• Transformation list: Uses a transformation list to find a value and set it in the target field.
• Number sequence: Uses a number sequence to set a value in the target field.
• Web service: Uses a web service to get a field value from another internal or external source and set it in the target field.
• Custom: Uses a custom action class to set the target field value.

For each enrichment rule, you can set up conditions to define the data to which the rule applies.

Note: You can only use enrichment rules if Data enrichment is turned on in the Data quality studio parameters, on the Enable data enrichment tab.

By default, a data quality policy version is applied to all organizations as defined in the current D365 F&SCM environment. If a data quality policy version must be applied only to specific organizations, set up the organization assignment.

For each validation rule, you can set up conditions. The validation rule is only applied if the conditions are met.

Use validation rules to check if the data is in line with the defined standards.
To validate data, you can use several validation types. This topic explains how to set up the Configurable lookup validation type.

Use a configurable lookup validation to add a custom lookup to a field and to validate if the field value matches a value as defined by the configurable lookup.

Note: If the field, to which the configurable lookup is applied, already has a lookup, the configurable lookup overwrites the existing lookup.

Before you can set up a configurable lookup validation rule, set up the configurable lookup to be used.

Use validation rules to check if the data is in line with the defined standards.
To validate data, you can use several validation types. This flow explains how to set up the Data pattern validation type.

Use validation rules to check if the data is in line with the defined standards.

To validate data, you can use several validation types. This topic explains how to set up validation rules of these types:

• Mandatory: Makes it mandatory to fill the defined field.
• Blank: Validates if no value is entered in a field.

Use validation rules to check if the data is in line with the defined standards.
To validate data, you can use several validation types. This flow explains how to set up a validation rule of type 'Query'. 

Use a query validation rule to validate if an entered field value is allowed using a dynamic query. Using a dynamic query, you can validate the field value based on one or more field values in another table. 

Examples of validations where you can apply a query validation rule:

• On creating a sales order, check if address information or contact information is defined for the selected customer. If no address or contact information is defined, the customer cannot be used on a sales order.

• On the worker setup, for the worker position, a cost center can be defined in the 'Cost center' financial dimension. Validate if the defined cost center is active. If not active, a warning or error message is given for the worker.

• On terminating an employee, check if positions are reporting to the employee. If positions are still reporting to the employee, you cannot terminate the employee.

Before you can set up a query validation rule, set up the dynamic query to be used.

Use validation rules to check if the data is in line with the defined standards.
To validate data, you can use several validation types. This topic explains how to set up the Web service validation type.

Use validation rules to check if the data is in line with the defined standards.

You can set up data quality policy rules that use a web service.

You can use a web service:

• Validation rule to validate if a field value matches a value in another internal or external source, using a web service.
• Enrichment rule to get a field value from another internal or external source, using a web service, and set this value in the target field of the enrichment rule.
• Action rule to get a field value from another internal or external source, using a web service, and set this value in the target field of the enrichment rule.