---
title: "Release 10.0.45.23 (September 2025) - Data Entry Workflow"
slug: "release-1004523-september-2025-dew"
description: "Explore the new features in Data Entry Workflow Release 10.0.45.23 (September 2025), including mass processing and mandatory field enforcement."
tags: ["Release notes", "Data Entry Wokflow", "DEW"]
updated: 2026-03-24T06:28:14Z
published: 2026-03-24T06:28:26Z
canonical: "docs.staedean.com/release-1004523-september-2025-dew"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release 10.0.45.23 (September 2025)

Find information on Release 10.0.45.23 (September 2025) of Data Entry Workflow for Microsoft Dynamics 365 D365 F&SCM.

## What’s new

New or changed features in Release 10.0.45.23 (September 2025) – Data Entry Workflow.

### 1. Mass Processing of Workflow Instances

This release adds a *Mass processing* capability so users can filter workflow instances by *Template* and *Step*, select records from a grid, and update them in bulk via a **Bulk Amend** page.

- Supports editing multiple instances at once, with a dynamic *Bulk Amend/Approve* action when the step includes approvals.
- All updates respect D365 validations, Data Quality Studio rules, enrichment policies, duplicate checks, and configurable lookups.
- Template designers can expose up to 25 editable fields for mass processing; tabular data and attachments are excluded.

Related documentation:

- [Do workflow tasks using mass processing](https://docs.staedean.com/data/Data Entry Workflow/en-us/BpmActivity_5637215828.html)
- [Mass processing data entry workflow tasks](https://docs.staedean.com/data/Data Entry Workflow/en-us/BpmConcept_5637167077.html)
- [Edit fields](https://docs.staedean.com/data/Data Entry Workflow/en-us/BpmActivity_5637167829.html)

### 2. Per‑Step Mandatory Field Enforcement

Mandatory status is now evaluated at runtime per step. Visual cues and validation reflect the field’s required/optional state for the *current* step only (e.g., required in Step 1, optional in Step 2).

Related documentation: [Edit fields](https://docs.staedean.com/data/Data Entry Workflow/en-us/BpmActivity_5637167829.html)

### 3. Connectivity Studio Test Mode Support

Templates in *Test Mode* can now execute for inbound data flows triggered by Connectivity Studio, removing the previous “inactive template” blocker for integrations. Manual user-triggered workflows still require an active template.

Related documentation: [Connectivity studio integration](https://docs.staedean.com/data/Data Entry Workflow/en-us/BpmConcept_5637148589.html)

### 4. Bulk Version Deletion from Template

Template designers can delete multiple template versions in one action, with safeguards:

- Active versions and the last remaining version cannot be deleted.
- Deletion is blocked for active/in‑use versions with a clear message.
- If nothing is selected, users are prompted to select at least one version.

**Compatibility**: Built for D365 F&SCM 10.0.45 and compatible with 10.0.42+. Integration, validation, and notification behaviors align with the core platform. Related documentation: [Delete workflow template versions](https://docs.staedean.com/data/Data Entry Workflow/en-us/BpmActivity_5637215826.html)

## Bug fixes

Bug fixes in Release 10.0.45.23 (September 2025) – Data Entry Workflow.

| Bug ID | Title | Description |
| --- | --- | --- |
| 223408 | Time zone misalignment on Address update | Effective-from/to date fields now populate based on the user’s current time zone. |
| 223947 | Conditions not triggered by default values | Conditions are now evaluated against default values so dependent logic runs as expected. |
| 225025 | Mandatory attachments blocked when tab is hidden | Mandatory validation no longer triggers for fields that are hidden by conditions in Data Capture or Approval steps. |
| 225027 | Financial dimensions not validated on tab/complete | Invalid financial dimension values are now validated and must be corrected before completion. |
| 226579 | Reference between tables not working | Lookup/dropdown values populated via reference setup now behave as expected. |