What's new in version 2505.5.0.0

Enhancements/Modifications

With this release of the Aptean Global Trade extension, the following changes have been made to ensure compatibility with Business Central, version 28.

The item tracking initialization method has been updated to use the new BC28 API structure. The InitFromPurchLine procedure call has been migrated from the Tracking Specification table to the Purch. Line-Reserve codeunit in the following locations:

• LoadJourney89FDW codeunit - The AssignLotNo procedure uses PurchLineReserve.InitFromPurchLine(TrackingSpecification, PurchaseLine) instead of TrackingSpecification.InitFromPurchLine(PurchaseLine) to properly initialize tracking specifications during journey load operations.

• JourneyStatinLotNoInfoPOs89FDW codeunit - The test codeunit has been updated with the same API change to ensure test coverage aligns with the production code.

Resolved issues

The following issues have been resolved in this release.

ID	Description
340636	The system fails to automatically populate the Weight Quantity (Kg) field value on the Item Tracking Lines page when importing a manifest file through the Manifest page and executing the Create & Release Purchase Order action for a catch weight item with license plate tracking.
340694	The system fails to retain the correct packaging location when loading a journey. Instead, the system updates the location code for all packaging items to the main location, causing items to be created or modified with incorrect warehouse locations and resulting in receipt issues during the purchase order processing workflow.
340679	An error occurs when creating a journey from a manifest after using the Use Grower Pallet ID toggle, even though the license plate does not exist in the system.
254968	An error occurs when executing the Load action on the Journey page. This issue arises when the Lot No. field value is assigned on the Purchase Order page for an item that has no Lot No. Series or Lot No. Profile field value on the Item Card page.