Release Date: 27 March 2026
Release Summary
- Fixed an issue where the Item Tracking Lines event subscriber incorrectly applied Sales Order master data templates to Transfer Order reservation entries, caused by a missing Transfer Line branch in the source type case statement.
- Resolved SQL exclusive lock conflicts on the SCB Master Data on Doc.Carrier table that occurred when multiple background sessions ran concurrently under the same service account.
Bug Fixes
Master Data on Documents
Fixed incorrect master data template applied to Transfer Order item tracking entries.+
The event subscriber for Item Tracking Lines did not include a case branch for Transfer Lines. When reservation entries were created for Transfer Order lines, the missing branch caused the system to fall through to default values, which matched the Sales Order template in the Master Data on Document Setup. This resulted in master data information records being incorrectly created against a Sales Order template in a Transfer Order context. The fix adds proper handling for Transfer Line source types so that unsupported source types are correctly skipped.
Resolved SQL lock conflicts on the Doc.Carrier table during concurrent background sessions.+
The SCB Master Data on Doc.Carrier table used only the User ID as its primary key, which meant that all background sessions running under the same service account competed for an exclusive lock on the same row. When two or more sessions (e.g. triggered by Azure Logic App) attempted to insert or modify master data information entries concurrently, the second session would time out with a lock conflict error. The fix eliminates the contention so that concurrent background sessions under the same service account can process master data without blocking each other.