What's new in version 2514.0.0.0

Release Note • 9/24/2025 • 14 min read

Features

With the features added in this release of the Aptean EDI extension,

Enhancements/Modifications

With this release of the Aptean EDI extension,

UI/UX changes

The following UI/UX changes have been made in this release.

Resolved issues

The following issues have been resolved in this release.

IDDescription
318863An error occurs on the EDI Messages page when processing the Aptean EDI 810 message that has multiple NoteRecord text elements associated with it.
320376The system incorrectly updates the bill-to customer details on the Sales Order page from the inbound file instead of using the details from the Customer Card page. This occurs even when No is selected in the confirmation message while processing the Aptean EDI 850 message with the USE_NAV_BILLTO port option set to Yes.
318870The system fails to calculate the Shipment Date field value in the sales header based on the value from the inbound file even though the Requested Delivery Date field value is defined when processing the Aptean EDI 850 message.
318256The system incorrectly calculates the Shipment Date field value on the Sales Order page based on the value from the inbound file even though the Requested Delivery Date field value is defined in the sales header when processing the Aptean EDI 850 message.
323232The system incorrectly displays an error message when processing the Aptean EDI 850, 860, or ORDERS D96A SalesOrderImp message if the GLN-related text elements for the customer or ultimate consignee exceed 13 characters. However, the system should ignore the GLN when its length is greater than 13 characters.
323897The system fails to update the Description field in the sales order line from the associated description field of the item charge when processing the Aptean EDI 850 and Aptean EDI 860 messages.
326198The system incorrectly displays an error on the Posted Sales Shipment page when the Ship-to Code field value is left blank on the Shipping FastTab while sending the shipment through Aptean EDI 856 Consolidated port.
323246The system fails to apply the correct EDI translation value for units of measure while processing the Aptean EDI 940 message, using only the first translation value instead of the value that matches the associated sales or shipment line.
324541The system fails to update the Unit of Measure Code field value on the Sales Order page from the associated item reference record when processing the ORDERS D96A SalesOrderImp message.
324397The system fails to update the Expiration Date field value on the Item Tracking Lines page for the lot number of an item when processing the RECADV D01B L4 WhseRcptImpBCW message.
321859The system displays an incorrect notification message while processing the inbound messages when the Inbound Post Processing field value is set to Release on the EDI Port Card page.
320512The system fails to update the HeaderAllowances, DetailAllowances, and TrailerAllowances sections for related invoices and credit memos while processing the INVOIC D01B Sales Credit Memo Outbound and INVOIC D01B Sales Invoice Outbound messages.
326514The system incorrectly generates multiple detail segments for an item from the reservation entry table, creating reservation entries even when no item tracking lines are defined while processing the Aptean EDI 940 message in a sales order. This issue occurs when the Order Tracking Policy field value on the Item Card page is set to Tracking.
322710The system fails to process inbound messages in the job queue if a message triggers a popup, such as Document was released, when the Auto Release option is defined on the EDI Port Card page.