You can start a data entry workflow from the forms to which it applies.
Depending on the dynamic menu form setup of a data entry workflow template, you can start a data entry workflow to create or edit a record.
If you create, edit, or delete a record using a data entry workflow template, a workflow task dialog is opened based on the initial step setup.
When you complete the initial workflow task, based on the applicable data entry workflow template setup, the next workflow task is created with the applicable assignment.
If a data entry workflow task is assigned to you, you can do the task.
The purpose of a data entry workflow task can be:
Data entry
Approval
Possible duplicates evaluation
Data entry
You can use a data entry workflow task for several purposes. This table explains the purposes:
Purpose
Description
Enter data
Fill in a set of fields as defined for the related step in the data entry workflow template.
If a grid is shown, you can enter several records.
Note:
If the task is to enter customer or vendor details for a new customer or vendor record, you can use the Name field to select a party that is already defined in D365 F&SCM. The party address details are automatically copied to the new customer or vendor record.
If the task is to delete a record, you cannot fill in any fields.
Review data
Review or reconsider a filled in value for which an approver did a change request.
Complete task
Complete the data entry workflow task. Based on the applicable data entry workflow template setup, the next workflow task is created with the applicable assignment.
Approval
You can use an approval step for several purposes. Depending on the step setup in the related data entry workflow template, you can have these options:
Option
Description
Edit
For an approval step, on the data entry workflow template, updating fields can be allowed. If so, as an approver, you can change field values directly on approval tasks.
Approve
The approver can approve by field or approve all fields at once.
If a grid is shown, you only can approve by grid record. If you approve the full approval task, the position of the approval step in the workflow defines the next action. If the approval step is:
The last step in the data entry workflow, the workflow is ended, and the entered data is transferred to the target tables.
An intermediate approval, based on the setup of the related data entry workflow template, the next workflow task is created with the applicable assignment.
Note: If the task is to approve a record deletion, you can only approve the full task. If approved, the record deletion confirmation message appears. Once confirmed, the record is deleted permanently and the workflow task is finished.
Change request
The approver can approve or request a change by field. For each change request, the approver can enter a comment to explain the requested data change for the field.
If for a field a change is requested, the Change request button becomes available. If the approver clicks the Change request button, the workflow task (step) where the field was initially filled in is reactivated with the applicable assignment.
Note: If the task is to approve a record deletion, you cannot request a change.
Delegate
The approver can assign the approval task to another user.
Reject
The approver can reject all fields at once. As a result, the data entry workflow is canceled. So, no next workflow task is created.
Possible duplicates evaluation
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. Based on the fuzzy duplicate check setup, each of the found possible duplicates gets a score. This score indicates to what extent the entered data is a duplicate.
Depending on the fuzzy duplicate check step setup, when possible duplicates are found, you can have these options:
Option
Description
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.
When a record is inserted or updated in a D365 F&SCM table for which data entry workflow SQL triggering is set up, the table event (Insert or Update) is logged in the Data synchronization log. To start a data entry workflow, you must process the logged table events from the data synchronization log. Usually, you process this in a recurring batch. The processing is done based on the Workflow template SQL trigger assignment.
As a result, the first data entry workflow task is created and assigned based on the data entry workflow template configuration. This topic explains how to process the data synchronization log.
Note:
For each SQL trigger that is defined and created in the database, all related table events are logged in the Data synchronization log.
Only the table event is logged and used for further processing. So, in case of an update, an event is logged of type Update. However, the changed data is not marked as changed and not used for further processing. For example, if you change a customer address, an event is logged that the customer is updated. However, the address change as such is not logged. When, for the logged event, a data entry workflow is started, the then current data of the customer is used.
If a logged event is processed, it is deleted from the data synchronization log.
A data entry workflow can be started by processing the data synchronization log. When you complete a related data entry workflow task, the inserted or updated records are only transferred to the applicable D365 F&SCM table if:
For the data entry workflow task, Transfer to target is Yes.
The data entry workflow task is the last step in the data entry workflow.