For Data entry workflow, an integration is available to Data quality studio.

The Data entry workflow-Data quality studio integration is automatically activated if Data quality studio is installed in the same environment as Data entry workflow.

General data quality check

When the Data entry workflow-Data quality studio integration is active, the applicable data quality policy rules are applied automatically to data entry workflows.

By default, if you run a data entry workflow, all active data quality policy rules that exist for the tables in the data entry workflow are applied. However, if, for a data entry workflow template, specific data quality policies are defined, only these data quality policies are applied when you run a data entry workflow.

These data quality policy rules can be applied:

Rule type Description
Validation rule

A validation rule checks if the data is in line with the defined standards.

When a validation rule is applied, depends on the validation rule event setup:

  • Field validation: On a data entry workflow task, validation rules are applied per field. So, when you have entered or changed a field value and you leave the field, the applicable validation rules are applied.
  • Record validation: For a data entry workflow, validation rules are applied when the entered data is transferred from the staging table to the applicable target tables. This can be for a task with Transfer to target enabled or for the last task of the data entry workflow.
Duplicate check rule

A duplicate check rule checks if the data doesn't already exist in a table.

For a data entry workflow, duplicate check rules of type 'Basic matching' are applied when entered data is transferred from the staging table to the applicable target tables. This can be for a task with Transfer to target enabled or for the last task of the data entry workflow.

To have duplicate checks done earlier, you can indicate if duplicate checks must be done for an earlier step.

If you have enabled duplicate checks for a step and a related task is completed, all applicable duplicate checks are done. The applicable duplicate checks are the ones that apply to the tables and fields for which data is entered so far in the data entry workflow.

If duplicate checks are applicable for a step, on task completion, these checks are done:

  1. Based on the primary key, does the entered data exist in the target tables? (Data entry workflow check)
  2. Does the entered data exist in the target tables? (Data quality studio duplicate check)
  3. Based on the primary key, does the entered data exist in another data entry workflow that is in progress? (Data entry workflow check)
  4. Does the entered data exist in another data entry workflow that is in progress? (Data quality studio duplicate check)

Note: In Data Quality Studio, you can enable merging duplicates for basic matching. If enabled, and possible duplicates are found, automatically, the Duplicate records found page is shown. You can compare the duplicates and merge field values. For more information, refer to Review and merge duplicates.

Enrichment rule

An enrichment rule sets a field value in a target field in D365 F&SCM.

When an enrichment rule is applied, depends on the enrichment rule event setup:

  • New record: The enrichment rule is applied when a data entry workflow task is created. So, default field values can be already set when you open a workflow task.
    Note: The priority in which default values are applied is: 1. Data entry workflow template field default value, 2. Data quality studio enrichment rule default value, 3. Standard default value. 
  • Source field modified: On a data entry workflow task, enrichment rules are applied per field. So, when you have entered or changed a field value and you leave the field, the applicable enrichment rules are applied. Note: If also validations rules apply to a field, these are applied before the enrichment rules.
  • Save record: For a data entry workflow, enrichment rules are applied when the entered data is transferred from the staging table to the applicable target tables. This can be for a task with Transfer to target enabled or for the last task of the data entry workflow. The enrichment rule is applied first and then the record is saved to the target table.
    Note: If also validations rules apply to the record, these are applied before the enrichment rules.

 

Note: If no active data quality policy rules exist for the tables of a data entry workflow, no data quality policy rules are applied.

Fuzzy duplicate check

In Data quality studio, you can set up and use a fuzzy duplicate check. This option checks for duplicates applying fuzzy logic. A fuzzy duplicate check compares values from several fields. based on the comparison, a duplicate score is calculated.
If Data quality studio is installed on the same environment as Data entry workflow, you can apply a fuzzy duplicate check in Data entry workflow.

For each data entry workflow template, you can define a fuzzy duplicate check step. Use a fuzzy duplicate check step to automatically check if the data, as entered in the previous workflow tasks, is a possible duplicate record.

During data entry workflow execution, for a fuzzy duplicate check step, the fuzzy duplicate check is done automatically. As a result of the fuzzy duplicate check, it can be that:

  • No possible duplicates are found. In this case, when the fuzzy duplicate check is finished, the data entry workflow is continued automatically. 
  • Possible duplicates are found. In this case, the assigned user gets a task to compare the entered data with the found possible duplicates. To solve duplicate issues, you can merge field values from the found duplicate records to the entered record. The entered record is called the master record. For more information on merging duplicates, refer to Check for, review, and merge duplicates.

For each fuzzy duplicate check step, define which options a user has when possible duplicates are found:

  • Approve: You can approve that the newly entered data is not a duplicate. When you click Approve, the data entry workflow is continued.
  • Delegate: You can assign the possible duplicates evaluation task to another user.
  • Reject: You can reject the newly entered data because it is a duplicate. When you click Reject, the data entry workflow is canceled.

Configurable lookups

In Data quality studio, you can set up a configurable lookup to define the possible options in a field.

A configurable lookup can be one of these types:

  • User defined list: The desired options are set up manually.
  • Dynamic query: A dynamic query is used to define the desired options.

In Data quality studio, you can apply a configurable lookup in a data quality policy, in a validation rule of type Configurable lookup. 

In a data entry workflow template, you can add a field for which a validation rule with a configurable lookup exists in Data quality studio. If the data quality policy is active, on a workflow task, the configurable lookup is applied automatically to the field. Also the validation rule conditions for the configurable lookup are considered.

Provide feedback