Transport Management
Release: Transport Management – 27.0.9692.37705
Description
This release delivers two critical bug fixes for the Transport Management extension, addressing issues with transport order warning management and landed cost assignment integrity. The first fix resolves a blocking scenario where users could not create multiple warnings with the same reason on a single transport order line, preventing repeated changes of the same type on source documents. The second fix corrects a data loss issue where posted landed cost assignments were deleted when using the edit feature on posted landed costs related to posted transport orders, which subsequently blocked invoicing. Translation files have also been updated across all supported languages.
User Stories
No User Story developed in this release.
Bugs
| Title | Description | Impact on previous version |
|---|---|---|
| [24203] – Cannot create multiple warnings with the same reason on a transport order line | When applying the same type of change more than once on a source document (e.g., updating packaging information multiple times), the system failed to create a second transport order warning with the same reason. The root cause was in procedure IsTransportOrderWarningReopenNeeded (Codeunit briTMS_TransportOrderMgmt, ID 71925905): a cross-reason filter lookup on packaging warning types incorrectly intercepted warnings of different packaging reasons on the same line. The fix collapses the two lookup branches into a single primary-key Get covering all six warning reasons (Source Quantity Updated, Source Cost Updated, Source Posted Quantity Changed, Packaging Information Created, Packaging Information Updated, Packaging Information Deleted), allowing multiple distinct packaging warnings to coexist and be independently created or reopened on the same transport order line. |
Low risk. The warning lookup is now more precise (exact primary-key match instead of cross-reason filter). Existing transport order warnings remain unaffected. No setup changes required. |
| [23484] – Posted landed cost assignments deleted when editing a posted landed cost linked to a posted transport order | When editing a posted landed cost (e.g., changing a fixed charge amount) associated with a posted transport order and clicking “Finish”, all posted landed cost assignments were deleted, making it impossible to invoice the posted landed cost. Two corrections were applied: (1) In Codeunit briTMS_TOApplicationEntriesMgt (ID 71925922), procedure CreateUpdatePostedLandedCostAssignmentOnCreateUpdatePostedLandedCosts — the field reference for SourceLineNoRef was corrected from Source Document Line No. to Posted Transport Order Line No., ensuring the correct line number is used for assignment lookup and creation. (2) Procedure CreateAssignmentForPostedTransportOrder now returns a Boolean value. In Codeunit briTMS_LandedCostSubscribers (ID 71925917), the subscriber AssignLandedCostsOnBeforeCreateAssignmentForDocumentLandedCost now evaluates this return value and, when false, executes a fallback via CreateAssignmentFromPostedLandedCost to ensure assignments are always created. |
Medium risk. The signature change of CreateAssignmentForPostedTransportOrder (void → Boolean) is a breaking change for any external extension calling this procedure directly. Existing posted landed cost assignments are not retroactively affected, but previously corrupted assignments (deleted by the old bug) may require manual correction. |
Events
No event added or updated in this release.