What's new or changed in Dynamics 365 Supply Chain Management 10.0.30 (November 2022)
This article lists features that are either new or changed in Microsoft Dynamics 365 Supply Chain Management version 10.0.30. This version has a build number of 10.0.1362 and is available on the following schedule:
- Preview of release: September 2022
- General availability of release (self-update): October 2022
- General availability of release (auto-update): November 2022
Features included in this release
The following table lists the features that are included in this release. We might update this article to include features that were added to the build after this article was originally published.
|Feature area||Feature||More information||Enabled by|
|Inventory and logistics||Track soft reserved quantities within allocations||Inventory Visibility inventory allocation||Enabled by service configuration|
|Manufacturing||Monitor equipment with Sensor Data Intelligence||Sensor Data Intelligence home page||Feature management:
(Preview) Sensor Data Intelligence
|Warehouse management||Multilevel detours for the Warehouse Management mobile app||Configure detours for steps in mobile device menu items||Feature management:
Multi-level detours for the Warehouse Management mobile app
Feature enhancements included in this release
The following table lists the feature enhancements that are included in this release. Each of these enhancements provides an incremental improvement to an existing feature. Because they are only enhancements, they aren't listed in the release plan. However, to ensure that these enhancements won't conflict with your existing customizations or preferences, each of them is turned off by default (unless otherwise noted).
If you want to turn any of these features on or off, you must do so in feature management.
|Module||Feature name in feature management||More information|
|Production control||On-hand information in production orders to release page||Adds a column for the on-hand inventory quantity for the line item in the lines section on the Production orders to release page.|
|Transportation management||Assign shipments to related route segments||This feature enables the system to apportion shipment freight costs more accurately, including for loads with multiple shipments delivered to various segment destinations along a single route. It assigns each shipment to the most suitable route segment based on the destination addresses of the shipment and segment. The feature then calculates each shipment's freight cost as a proportion of the load's total freight cost, based on the shipment's relative weight, volume, quantity and distance traveled. This feature only applies to shipments managed using the Transportation management (TMS) module.|
Platform updates for Finance and Operations apps
Microsoft Dynamics 365 Supply Chain Management 10.0.30 includes platform updates. To learn more, see Platform updates for version 10.0.30 of Finance and Operations apps (November 2022).
For information about the bug fixes included in each of the updates that are part of version 10.0.30, sign in to Lifecycle Services (LCS) and view the KB article.
Dynamics 365 and industry clouds: 2022 release wave 1 plan
Wondering about upcoming and recently released capabilities in any of our business apps or platform?
Check out the Dynamics 365 and industry clouds: 2022 release wave 2 plan. We've captured all the details, end to end, top to bottom, in a single document that you can use for planning.
Removed and deprecated Supply Chain Management features
The Removed or deprecated features in Dynamics 365 Supply Chain Management article describes features that have been or are scheduled to be removed or deprecated for Supply Chain Management.
- A removed feature is no longer available in the product.
- A deprecated feature is not in active development and may be removed in a future update.
Before any feature is removed from the product, the deprecation notice will be announced in the Removed or deprecated features in Dynamics 365 Supply Chain Management article 12 months prior to the removal.
For breaking changes that only affect compilation time, but are binary compatible with sandbox and production environments, the deprecation time will be less than 12 months. Typically, these are functional updates that need to be made to the compiler.