Release 10.0.49.30 (September 2026)

New or changed features in Release 10.0.49.30 (September 2026) of Data Entry Workflow.

1. Cross-table grid support for address fields

In Data Entry Workflow, you can use a grid in a data entry workflow step to enter several records in one step. A grid is normally based on one table.

An exception is introduced that applies to address and contact information for customers and vendors. In D365 F&SCM, customer and vendor address and contact information is stored in several related tables. Usually, you would need a separate data entry workflow step or field group for each related table.

For customer and vendor addresses and contacts, you can now enter this data in one grid instead. On the workflow task, you can enter several addresses or contact information lines, even though the data belongs to different tables.

On data entry workflow execution, for change requests and fuzzy duplicate checks, each grid line is handled separately.

Note

Before you create multi-table grid templates, close and deactivate all existing workflows related to the customer/vendor address. This releases the temporary tables and cleans up the custom fields. If you skip this step, a custom field error can occur.

See also:

• Configure step with wizard - Customer

• Configure step with wizard - Vendor

• Edit field group details

• Do workflow task

• Multi-table grid in a data entry workflow

2. Virtual field support in calculated fields

In Data Entry Workflow, you could only define physical fields as calculated fields. And in the calculation expression you could only use physical fields as variables.

This is now extended: You can define both physical fields and virtual fields from the workflow document as calculated fields. You can also use both physical and virtual fields as variables in the calculation expression. For example, you can now use product attribute fields (virtual fields) as calculated fields or in the calculation expression

See also: Set up calculated fields for data entry workflow template

3. Product attributes in fuzzy duplicate check

You can now set up a fuzzy duplicate check on product attributes in Data Entry Workflow. If duplicate values are found, the assigned user can review and merge them on the workflow task.

See also:

• Product attributes in fuzzy duplicate check

• Do workflow task

4. Step assignment extended with types Hierarchy and Field

In Data Entry Workflow, you could assign a data entry workflow step to a user, role, or team.

Two new assignment types are introduced: Hierarchy and Field.

4.1 Hierarchy

You can now use a workflow step assignment of type Hierarchy to determine the workflow step assignee. To complete the setup, define the hierarchy and hierarchy level.

The workflow determines the assignee as follows:

1. It identifies the user who started the workflow.

2. It locates this user's position in the selected hierarchy.

3. It goes up the defined number of levels from this position.

4. It assigns the step to the user found at that level.

4.2 Field

You can now use a workflow step assignment of type Field. To complete the setup, define a field from the workflow document that represents the assignee. Make sure this field is filled in during an earlier step of the workflow. To indicate the type of value, also define the Field type: User ID, Worker record ID, or Personnel number.

If the assignment type is Field, you can also apply a hierarchy and hierarchy level. In this case, the workflow determines the assignee in the same way as for the type Hierarchy. However, it starts with the assignee defined in the field, instead of the user who started the workflow.

See also: Set up step assignment

5. Monitoring workflow - No step assignments

In Data Entry Workflow, on workflow step creation, it can occur that no active user can be assigned. This blocks the workflow for further processing. To solve this, we have implemented error detection and enabled manual user assignment.

5.1 Error detection

If a workflow step is created without any users assigned, it moves to the Error status, and and error message is shown. The error message states the step name, and that no active user is found for the configured assignment.

An assignment error can have several causes, for example:

• A step is assigned to a team, but all users in the team are inactive.

• A step is assigned to a security role, but no active users are linked to this role.

• A step is assigned to a hierarchy position, for example a manager. Due to organizational changes, for example when an employee leaves, this position is temporarily vacant.

5.2 Manual user assignment

For a step without an assignment, the Add user assignment button is available. As a Data entry workflow manager, you can manually assign an active user. You cannot assign the step to a team or a security role.

See also: Troubleshoot data entry workflow - Assignment issues

6. Exclude non editable fields from change request at approval step

In a data entry workflow, for a data entry step, a field can be marked as Non-editable. On a next approval step, it doesn't make sense to do a single-field approval or change request.

From this release, on an approval step, you can not:

• Approve a single field if it is marked as Non-editable in an earlier data entry step.

• Request a change for a single field if it is marked as Non-editable in an earlier data entry step.

See also: Do workflow task

7. Data entry workflow monitoring - Tracking details extended

Two fields are added to the workflow tracking details to improve the step history tracking and reviewing:

• Action taken: Indicates the action button that is chosen on the workflow task.

• Comment: Shows the comment entered in case of these approval actions: Rejected, Delegated, or Change Requested.

See also: Monitor data entry workflows

8. Rejection comments enabled as placeholder in notifications

You can now use the %RejectionComments% placeholder in email notifications. This placeholder inserts the comments entered when someone rejects data in an approval workflow task.

See also: Set up notification

9. Hover details for lookup fields in workflow tasks

In a Data Entry Workflow workflow step (data entry or approval), hovering over a lookup field value now shows a tooltip with the key details of the selected record, matching the standard hover behavior in Microsoft Dynamics 365 Finance & Supply Chain Management. This works automatically, without additional template configuration.

See also:

• Start workflow

• Do workflow task

10. STAEDEAN Common Library

Bug fixes in Release 10.0.49.30 (September 2026) of Data Entry Workflow.

Known issues in Release 10.0.49.30 (September 2026) of Data Entry Workflow.