All functionality described in previous release notes still are available unless described otherwise in this document.<\/p>\n
<\/p>\n\t
Productivity Enhancements<\/h2>\n
\nGeneral<\/h3>\nSaving ID of order creator<\/h5>\n
Saving ID of order creator<\/h5>\n
When an order is archived, an entry is made in the database containing the ID of the creator of the order. Information in the entry is restricted to the user who created the archived version.<\/p>\n
Saving lot related attachments to Sharepoint<\/h5>\n
It is now possible to create a connection between Document Capture drag and drop directly to lot number screens.<\/p>\n
Additional fields and options in case of an external warehouse<\/h5>\n
Order screens related to sales, purchases and transfers allow storage of an external number triggered by external communication.<\/p>\n
Colour indication based on status table<\/h5>\n
The master data status table is enriched with a colour indicator connected to statuses. Chosen colour will be displayed on all related screens such as customers, vendors, items and lot numbers, as well as purchase, sales and transport. Column may need to be added through personalization\/customization.![\"\"](\"http:\/\/help.hbsoftware365.com\/wp-content\/uploads\/2025-Q3-G1.png\")
<\/p>\n
\n
Finance<\/h3>\nCurrency contract entry on lot number card<\/h5>\n
A currency contract may be added to a lot regardless of the presence of related data in the HBST currency contract table.<\/p>\n
Removing lines with 0 amount from cost calculation<\/h5>\n
Cost templates setting allows lines containing 0 cost to be excluded from the calculation. Additionally, calculation card contains a function which executes deletion of 0-amount lines. Value eligible for removal is editable.![\"\"](\"http:\/\/help.hbsoftware365.com\/wp-content\/uploads\/2025-Q3-F1.png\")
<\/p>\n
\n
Sales<\/h3>\nReservation of lots from blanket orders displayed in CU (Consumer Unit)<\/h5>\n
When lot reservation is made from a blanket order line, it is set to show quantities in CU.<\/p>\n
Copy reserved lot from blanket order to sales order<\/h5>\n
Lot information is now copied to the tracking lines of a sales order when created from a blanket order line carrying lot reservation.<\/p>\n
Status\/colour on sales order line<\/h5>\n
A new feature is added to the master data status screen, allowing a coloured status field to be added to sales lines. If applicable, a line level calculation will be conducted to check lot availability. Based on the outcome, status of the sales order line will be adjusted.![\"\"](\"http:\/\/help.hbsoftware365.com\/wp-content\/uploads\/2025-Q3-S1.png\")
<\/p>\n
\n
Supply Chain<\/h3>\nItem ledger price adjustment related to CU quantities<\/h5>\n
Adjusting quantity per consumer unit of measure will now correct related information in item ledger entries.<\/p>\n
Container number from purchase order to transfer order.<\/h5>\n
When creating a transfer order from a purchase order, container number is now copied from purchase order to transfer order.<\/p>\n
Default location from vendor card upon purchase order creation.<\/h5>\n
System will now copy a location from a vendor card to purchase order creation. If no value is present, field remains empty.<\/p>\n
Editable fields in posted purchase receipts<\/h5>\n
Number of editable fields related to planning on posted purchase receipts is reduced.<\/p>\n
Destination location check removed when retrieving transfer lines<\/h5>\n
When fetching container lines from a transfer order, a check is performed on destination location in purchase order receipts. If the shipment is redirected for a different destination location, container line retrieval fails. This is now corrected.<\/p>\n
Corrected available actions to item ledger entries screen<\/h5>\n
Accessing item ledger entries from vendor\/customer ledger entries will now show a screen with appropriate actions. Before there were no actions available on item ledger entries screen when being accessed through said route.<\/p>\n
Lot numbers on posted transfers<\/h5>\n
Lot number is now visible directly on posted transfers.<\/p>\n
Notify party fields<\/h5>\n
Field added to select notify party on purchase header and transport order.<\/p>\n
Changing location on assembly orders with active tracking lines<\/h5>\n
Changing a location of an assembly order with active tracking lines can be now done via function ‘change location’ in the assembly order header section.<\/p>\n
Transport lines screen added<\/h5>\n
Added transport lines screen is accessible through item screens, lot number screens and through menu.<\/p>\n
Sorting transfer orders, warehouse shipment\/receipt<\/h5>\n
Sorting of warehouse documents and transfer orders is now responding to sorting options found in SmartTrade Setup and User Setup.<\/p>\n
Show item ledger entries on transport order item ledger entries<\/h5>\n
Option added to transport order lines to view item ledger entries based on selected line.<\/p>\n
Create transfer for transport order<\/h5>\n
It is now possible to create a transfer order for a transport order. Doing so directly changes status on the transport order.<\/p>\n
Transfer order creation from posting transport order<\/h5>\n
Posting a transport order results in automatic creation of a transfer order.<\/p>\n
Order of purchase date fields ERD calculation<\/h5>\n
The calculation of the Expected Receipt Date is revised. Confirmed CRD (Cargo Readiness Date) is used as base date if available. If confirmed CRD is not available, confirmed ETD (Estimated Time of Departure) will become base date for calculations.<\/p>\n
\n
Traceability<\/h3>\nAdding colours to lot numbers<\/h5>\n
It is now possible to colourize lot numbers, for example, based on the lot’s status. Colours are accessible through page ‘SmartTrade master data status list’<\/p>\n
Display lot number in sales and purchase line details fact boxes<\/h5>\n
The lot number is added to purchase line details and sales line details fact boxes.<\/p>\n
\n
EDI<\/h3>\nEDI check on customer’s invoice address<\/h5>\n
When releasing an order for a customer who always processes everything via EDI, the order customer’s PO box address was used for validation. However, in case the invoice customer is a different customer, validation needs to be adjusted appropriately.<\/p>\n
EDI IV address field value not required for order release<\/h5>\n
Some EDI clients don’t include an IV segment resulting in IV segment not included in the order. A block is currently placed on this segment upon order release, but that shouldn’t be necessary; it should be sent to the invoice customer’s IV address. Therefore, the invoice customer’s IV address must be included when creating the EDI order.<\/p>\n
Deleting old EDI messages and envelopes<\/h5>\n
It is now possible to delete old EDI messages and envelopes. This can be done by checking the date filter set in the EDI settings.![\"\"](\"http:\/\/help.hbsoftware365.com\/wp-content\/uploads\/2025-Q3-ED1.png\")
<\/p>\n
\n
Cost calculation<\/h3>\nOrder type setting automating cost calculation<\/h5>\n
Order type setting was added for automatic calculation creation in case no calculation was made.<\/p>\n
Reservation deletion when deleting blanket order lines<\/h5>\n
If a blanket order line is deleted, any reservations made on purchase orders and transfer orders are deleted as well.<\/p>\n\t
Did you know?<\/strong><\/p>\n When selecting an item line on any order screen, the following shortcuts can be used?<\/p>\n Alt+L\u00a0 \u00a0 \u00a0 \u00a0->\u00a0 \u00a0 Lot No. Information List and<\/p>\n CTRL+L\u00a0 ->\u00a0 \u00a0 SmartTrade Item Lot Availability<\/p>\n\t Solved error regarding insufficient memory occurring when adjusting the calculation quantity for a sales order based approached from a blanket order.<\/p>\n When adding email body texts with more than 10 lines, an error occurred on line 10 when sending the email.<\/p>\n The filter on the tile with my sent tasks was incorrect. As a result, only your own, open tasks that you created were sent.<\/p>\n When deleting a cost calculation, the cost summary was not always deleted.<\/p>\n Cost price and sales price per CU were not calculated correctly.<\/p>\n Error message resolved occurring upon assignment of charges directly to purchase invoice lines.<\/p>\n The pallet requirement field from the shipping address was not transferred to the sales order.<\/p>\n The calculation of the ERD was not always correct. An option was added to work with expected dates or actual dates. The expected receipt date on a line was not always updated correctly if the time to warehouse was unknown.<\/p>\n Volume calculation was only working with cm\u00b3 unit of measure. Correction made to have volume calculated based on m\u00b3.<\/p>\n When retrieving the standard purchase text with a link to the manufacturer, an error was likely to occur because the manufacturer table was being used instead of the SmartTrade Manufacturer table.<\/p>\n If the transport time field was filled in while ETA entry point field already contained a value, ETA entry point field was still adjusted.<\/p>\n Linked vendor texts were not transferred to a newly created purchase order in all situations.<\/p>\n The price per CU was calculated incorrectly, the price was multiplied when it needed to have been divided.<\/p>\n When dividing a purchase order (line) across multiple transport orders, data was not retrieved correctly in all cases. Quantities from a previous order (booked quantity) were not considered. Furthermore, the status of a purchase related transport order was not updated after booking if the status table was not filled in.<\/p>\n If no container was linked to a purchase order, the sum of all containers was displayed in the fact box, while it should have been 0.<\/p>\n Corrected: EDI import of correct EAN.<\/p>\n Corrected: EDI import includes GTIN.<\/p>\n When releasing a purchase order containing an assembly item, (if configured) a lot number was created for the purchase line. However, an assembly order is also created later with a lot number, resulting in duplicate entries.<\/p>\n When creating a new lot number, the default status for a new lot is now checked in the status table. Status including colour is then applied to the new record.<\/p>\n <\/p>\n When processing an EDI message to a sales order, the correct GTIN code was not always transferred to the sales order.<\/p>\n When importing EDI messages, the external document number was not always retrieved due to inconsistencies in EDI message structure.<\/p>\n When importing some EDI order files, the external reference number was missing because it is sometimes located in a different location in the BGM line.<\/p>\n It was not possible to enter a 14-character GTIN code, although this should be possible when, for example when printing an ITF14 barcode.<\/p>\n When posting a manually entered EDI order whose dispatch advice should be sent as a DESADV message, an error occurred due to a missing line number.<\/p>\n When converting an assembly item to component lines, the corresponding extended text lines were not included to be transferred.<\/p>\n Update 26.3 for Business Central 2025 release wave 2 (Jul. 2025)<\/a><\/p>\n Update 26.4 for Business Central 2025 release wave 1 (Aug. 2025)<\/a><\/p>\n Update 26.5 for Business Central 2025 release wave 1 (Sep. 2025)<\/a><\/p>\n <\/p>\n Check out link below for highlight videos of the most recent release, features available to try and plans for upcoming features.<\/p>\nProblems solved<\/h2>\n
\nGeneral<\/h3>\n
Error resolved: Insufficient memory<\/h5>\n
Error resolved: email body text longer than 10 lines.<\/h5>\n
My sent tasks information is incorrect.<\/h5>\n
\nFinance<\/h3>\n
Document Cost Relation table was not cleared when deleting calculations.<\/h5>\n
Displaying cost price\/sales price per unit in item entries incorrectly.<\/h5>\n
Error resolved: Item charge assignment in purchase invoice<\/h5>\n
\nSales<\/h3>\n
Pallet requirement not transferred from shipping address to order<\/h5>\n
\nSupply Chain<\/h3>\n
Calculation of ERD (Estimated Receipt Date) incorrect<\/h5>\n
Volume in m\u00b3 is not calculated<\/h5>\n
Error retrieving text lines for preferred manufacturer<\/h5>\n
Entering ‘Transport time to destination’ adjusts the ETA entry point.<\/h5>\n
Vendor texts not transferred to purchase order<\/h5>\n
Corrected prices per CU in item entries.<\/h5>\n
Split purchases across multiple transport orders<\/h5>\n
The container count on the purchase overview was incorrect.<\/h5>\n
Error resolved: missing container settings<\/h5>\n
Import EDI met foute EAN<\/h5>\n
Import EDI zonder GTIN<\/h5>\n
\nTraceability<\/h3>\n
Assembly item on purchase, no lot creation<\/h5>\n
New lot must be assigned the correct colour immediately.<\/h5>\n
\nEDI<\/h3>\n
EAN number is empty when processing message to order<\/h5>\n
EDI message does not contain external document number<\/h5>\n
EDI does not import reference number<\/h5>\n
EDI with 14 characters cannot be entered as a GTIN per unit<\/h5>\n
Error when posting a manually entered EDI order<\/h5>\n
\nExtended text<\/h3>\n
Item text lines not transferred from assembly item to component<\/h5>\n
Recommended links<\/h2>\n\t