Logtrade Connect

Business Central 23.3 and later

24.3

It was not possible to extend the permission sets.

24.2.330.0 (2025-01-08)

New settings on shipping agent service and package type relation for automatic handling of EUR-pallets when sender or recipient are missing EUR pallet customer number.
Fetching status från Logtrade could generate a duplicate error for tracking entries
It was not possible to track on shipping agent website from the list of tracking entries.
Pushing delivery date forward due to Latest Pickup Time on shipping agent service did not work if the shipment date on the source document was in the past.
No. of EUR Pallets has been removed fron Sales Header (since it was not used).

24.1.328.0 (2024-12-17)

Creating consignment(s) from warehouse shipment will now reuse consignment(s) created from warehouse shipment if these are prepared AND booked.
A new action on warehouse shipment to create consignemnt(s) for all lines regardless quantity to ship to enable booking before pick if Warehouse Qty. Calculation is set tp "Qth. to ship" (which is default).
Booking a consignment from the consignment list did not save the booking status.

24.0.323.0 (2024-12-16)

It was not possible to delete a sales order

24.0.322.0 (2024-12-13)

A Christmas release that comes with a christmas gift: Delivery Options

Alignment with the new number series functionality in BC24.
Unit Price (LCY) and Amount (LCY) has been reintroduced in Consignments cost in parallel with Unit Price and Amount in foreign currency.
Load meters has been added to the Qpick API.

23.36.317.0 (2024-12-05)

Changing customer number on a sales document did not clear existing ship-to phone no., ship-to email and ship-to mobile phone no.
It was not possible to rename an item with number longer than 20 characters if the item had variants.
It was not possible to post a warehouse shipment linked to a service order if the setup was set to empty source document tracking number on delivery.

23.35.312.0 (2024-12-02)

It was not possible to open the list of shipping agent services.

23.34.310.0 (2024-11-26)

The user can now manually change the set system filters in the consignment journal.
It was possible to reuse a booked consignment even if the shipping agent/-service code was changed on the warehouse document.
Expiration Date was not calculated on package item line for pick lines with lot number.
Item Quantity Calculation did not work in all scenarios since version 23.31.302.0.

23.33.307.0 (2024-11-22)

It was not possible to change Shipping Agent or Shipping Agent Service Code in the Freight Cost Calculation page.
It was not possible to create a consignment from a source document with automatic timetable query enabled on the shipping agent service.
A consignment created based on consignment creation rules was not sent to Logtrade since version 23.31.302.0.

23.32.304.0 (2024-11-20)

External http requests are now enabled by default when running the assisted setup in a sandbox environment.
Using Warehouse Posting Date as Shipment Date did not work as expected.

23.31.302.0 (2024-11-19)

Splitting a pick line lead to wrong item quantities in consignment if Warehouse Quantity Calculation was "Quantity" in Delivery Setup.
Currency Code has been added to cost calculation rules.
A linked source document with the same document number as on the consignment are now ignored when receiving a consignment creation request in the Qpick API.
A new option for consignment shipment date calculation has been added to the delivery setup: "Warehouse Posting Date" which affects consignments created från warehouse shipment, warehouse pick and inventory pick.
Default services were not calculated correctly for default shipping agent/-services.
Using a resource as cost created a consignment item line if an item with the same number as the resource existed.
A new setting on cost code: "Customs Invoice Charge Type" with values blank (default), Freight and Insurance. Customs invoice charges are summed up and sent to Logtrade on invoice header level.
Booked consignments created directly from source documents are now reused when creating consignments from warehouse shipment, warehouse pick and inventory pick.
A booked consignment will send a new booking request if the consignment is reopened and prepared again.

23.30.297.0 (2024-10-18)

Weight calculation did not work on inventory pick if bin was mandatory on the location.
Consignments created from release of warehouse shipment are now deletet (if not sent to Logtrade) automatically if the shipment is reopened.
If consignments created by releaseing a source document (or warehouse shipment) could not be deleted (because they have been sent to Logtrade), these consignment can now be opened in a list for manual deletion.
Volume was not calculated on Sales Order when validating No. of Packages.
The assignment of Shipping Agent code and Shipping Agent Service code on Sales Shipment based on a consignment did not include assignment based on released consignment.
Sales Shipment and Outbound Transfer now inherit Shipping Agent Code and Shipping Agent Service Code från Inventory Pick.
"LTC Cons. Tracking No. Serie" in Shipping Agent Service has been extended to 20 characters.
There were an issue with duplicate instruction lines when creating sales order through a customer API.

23.29.295.0 (2024-10-14)

It was not possible to setup field mappings to custom fields on consignment and consignment address.
Double freight lines were inserted on inventory pick if bin code was mandatory.
Decimal digit was not treated correctly when fetching packages from Control Tower.

23.28.292.0 (2024-10-09)

It was not possible to manually input more than two decimals in consignment item lines.
The Logtrade Connect app are now automatically allowed for external http requests when creating a new sandbox environment.
Duplicate package IDs when fetching packages with GetStatus are now ignored even if duplicates should not occur.
The permission set LTC TRACK was not added automatically to the Entra-app for tracking push.

23.27.289.0 (2024-10-03)

There were references to, and logic tied to, the setting for "Directed Put-away and Pick" on Location. This has been changed to "Pick Required".
Mobile Phone No. has been introduced on location.
We have made it possible to fetch items to package from posted and registered picks.
If an instruction/text was specified on a ship-to adress, all instructions/texts were deleted and replaced with thos from the ship-to address. This replacement is now per instruction/text type.
It was not possible to get package lines and packages from Control Tower.
Freight Cost Calculation from Sales Order has been refactored so it can be called by "Sales Header".LTC_CalcFreightCost.
Freight Cost Calculation now sets current datetime in the field "Sales Header"."LTC Freight Charge Date/Time" on a successful freight charge calculation.
A new consignment creation event: Release Warehouse Shipment.

23.26.286.0 (2024-09-20)

It was not possible to set Terms of Delivery Location using field mapping.
Multiple sets of texts based on text rules could be cretated in some scenarios.
Specifying default document type in Delivery Setup could cause additional services not to be created for consignment.
Creating a consignment from a package based on a Warehouse Pick did not created linked source documents.
Creating a consignment using the consignment API did not trigger dangerous goods creation.
Confirming a consignment using the consignment API did not return an error when a validation error occured.
The consignment API did not create packages.
The consignment API can now recieve a print queue name to direct the printing to the desired printer.

23.25.284.0 (2024-09-09)

A new API for creating consignments without first creating packages. Click here to learn more.
It is now possible to calculate freight charge on posted sales shipment and posted service shipment and have the order updated with the freight cost.

23.24.282.0 (2024-09-04)

The fields Payer and Paying Customer No. on consignment are nov visible or hidden depending on if the consignment is domestic or not and the setting Use Payer on the terms of delivery relation.
A manually performed validation of delivery data on a sales order prevented the order from being released. Prevention from release is now only performed if an applicable rule for sales order validation has "Validate on release" = true. This means that manual validations are now only informational.
It was not possible to resend a consignment request using the Qpick API.
The Qpick API now calculates shipment date on consignment the same way as the web client.
Max. Weight and Max. Volume can now be specified on shipping agent service. This setting controlls the default assignemnt of No. of Packages on Consignment Package Line.
Creating package item lines using the API did not update Qty. to/on Package on pick line when a Source Document Line No. was supplied in the request.
It was not possible to ship a transfer order which had a package tracking number.

23.23.280.0 (2024-08-26)

It was not possible to open the list of released consignments from posted shipments.

23.22.278.0 (2024-08-21)

The selection of "put lines" when calculating items based on pick lines was previously based on if the location had directed pick/put away. This has been changed so it depends on if bin is mandatory or not.
A new setting in Consigment Creation Rules that allows creation of consigment when a warehouse shipment is created.
Tracking No. on service order, transfer order and purchase return order.
Tracking No. and functionality for tracking on service order shipment, transfer shipment and purchase return shipment.

23.21.276.0 (2024-06-28)

A new event "LTC Package Release".OnBeforeInsertReleasedPackageItemLine to enable transfer of extension fields to released package line.

23.20.274.0 (2024-06-25)

API version 1.3 where Package.ConfirmConsignment now expects the parameter printQueueName in the payload (can be blank)

23.19.272.0 (2024-06-19)

Manually entered package item lines no longer triggers a reload of consignment items based on package items (as in pre version 23.18.270.0)

23.18.270.0 (2024-06-19)

Manually entered customs invoice information on consignment could be overwritten with default values from Delivery Setup.
Items (if exists) package are now always used to populate consignment items.
sourceDocLineNo is now exposed in the API for creating package.

23.17.267.0 (2024-06-17)

Duplicate Carrier Product, Carrier Product Services and Package Types reported by Logtrade are now ignored when updating carriers from Logtrade.
New settings in Delivery Setup that determines if Item Unit of Measure shall be used for weight/volume calculations.
Changing Shipping Agent and/or Shipping Agent Service Code on Warehouse Shipment, Warehouse Pick or Inventory Pick now use default services and services parameter values for the specified Shipping Agent /-Service. Any services that has been altered manually on the source document will be preserved.

23.16.265.0 (2024-06-10)

Settings on Shipping Agent Service for calculation of weight/volume were not respected on a package not yet linked to a consignment.
An error could be thrown about Consignment not existing when sending a consignment to Logtrade and delivery note is enabled.

23.15.263.0 (2024-05-29)

Validation of sales order no longer filter sales order lines based on the location code of the sales order header.
Using the "LTC Package".AddToConsignment(true) caused duplicates in Consignment Item Line if there were more than one package linked to the consignment.
It was not possible to specify Transfer-to Code on a transfer order if Transfer-to Code was moved to be the first control on the page.
Item descriptions in customs invoice was truncated to 35 characters for all carriers, not only PostNord.

23.14.260.0 (2024-05-21)

Long item descriptions could cause an issue in Delivery Note (since version 23.13.258.0).
Item descriptions in customs invoice are truncated to 35 characters for PostNordSweden.

23.13.258.0 (2024-05-17)

A new setting on Carrier: "Max String Length". Default is 35 characters for PostNord Sweden since PostNord has restrictions for string lengths in their new API. This setting affects item description on delivery note and delivery instructions.
A new overload for the bound method ApiConfirmConsignment on the API page "LTC Package v1.2" has been added that accepts a print queue name.
Eori on Company Information and Customer now syncs to the Address Identifier type Eori (instead of EoriGB as before).
Existing EoriGB identifiers that does not start with "GB" are moved to Eori identifiers.
Logic based on recipient country that decides if Eori, EoriGB or Voec shall be used has been introduced.
The custom layout for customs invoice did not use signee and signee position from the consignment.
The custom layout for customs invoice now selects Eori/EoriGB/Voec based on the country of the recipient.
Package Type Code and Print Layout Code has been added to the primary key in Custom Print Rule to allow multiple print layouts for e.g. the same country.
Sales Order validation on manual release was run for all sales document types.

23.12.251.0 (2024-04-25)

The possibility to print a signature image has been added to the custom print layout for customs invoice.
Usability enhancements in Consignment Error List and Web Service Communcation Log.
Subscriptions for services, texts and instructions were triggerd by temporary data (causing issues in e.g. PEPPOL-export).

23.11.249.0 (2024-04-17)

Fetching items to a package only worked if package was create from a pick document.
Send Action settings now overrides a consignment creation request from Qpick where Qpick sends Action = 1 (prepare).
A Custom Print Layout has been created for Customs Invoice. This means that customs invoice can be printed directly towards Logtrade print service (and Integrated Printer) based on a design specified as a custom print layout in Business central.
If Net Weight or Gross Weight or Volume is missing on a source document line these values will now be fetched from the item card to the consignment item line.

23.10.245.0 (2024-04-12)

It was not possible to create a consignment from Qpick.

23.9.243.0 (2024-04-12)

Goods Included for weight- and volume settings was not respected by the Qpick integration.
Package item line was not created for assembly items fetched from registered pick.
Releasing a consignment could raise an error on Record Link already exists.

23.8.241.0 (2024-04-08)

Validation of delivery information on sales order now includes customs invoice data even if the future consignment will have a From Split Point Code. This will take care of validations specific for customs invoice such as Net Weight, Tarrif No. etc.
Validation of delivery data on sales order did not stop automatic creation of consignment with action "Save" if error occurred during validation.
Manually fetching items from a pick document to a package presented the user with double source lines if the location were setup for directed put-away/pick.
Mixing pick from inventory with assembly on the same sales order line resulted in wrong walues in "Quantity on Package" when manually fetching items from a pick to a package.

23.7.239.0 (2024-04-03)

Changing packet type code on a consignment package line that has been created by manually adding a package to a consignment resulted in new automatically credated packages.

23.6.237.0 (2024-04-03)

Automatically created packages were not updated with item weights in a very specific setup/process scenario.
Passed shipment date are now replaced with current date (based on Today()) when sending a consignment for prepare (or release without a previous prepare).
Fetching items from a pick document to a package will now fetch items from the registered pick if the pick specified on the consignment no longer exists.
Package items and sub package lines where left oprphaned when an automatically created package was deleted by deleting a consignment package line.
A sales order will now be validated based on transport validation rules even if a previous manual validation has resulted in Transport Validation Status = Approved.
Error handling when downloading time table data to a consignment.

23.5.235.0 (2024-03-27)

A number of subscribers for Sales Header were triggered also for invoice and credit memo.

24.4.233.0 (2024-03-25)

It was not possible to specify vendor no on a purchase document that wasn't inserted in the database.
The app is now avaliable for Polish tenants.

23.3.231.0 (2024-03-19)

Source Document No. has been removed (obsoleted) from the service rule table since services for individual source documents are managed in a separate table.
"Delivery Category Code" has been introduced on all sources (customer, vendor etc.), all source document types and consignment as a generic way of categorizing data. A delivery category can represent anything that requires some kind of special handling in the delivery process. In this first iteration we are focusing on services.
Delivery Category Code has been added to the service rule table which enable specifying different service rules for different delivery categories.
Shipment Method Code has been added to the service rule table which enable specifying different service rules for different shipment methods.
Delivery Category Code has been added to the default service parameter value table which enable specifying different default parameter values for different delivery categories.
Shipment Method Code has been added to the default service parameter value table which enable specifying different default service parameter value for different shipment methods.
Sort Code, Budbee Order ID and Budbee Token were missing on Sales Shipment Header.
Several fields from Sales Header were missing in Sales Header Archive.
Support for Sales Quote:
- Calculation of freight cost
- Free texts
- Instructions
- Services
Booking reference was not sent together with customs invoice.
Declared value was sent together with customs invoice.
The step where services can be reviewd/added in the freight cost calculation has been remowed since services can/should be added to the quote/order before the freight cost calculation is executed. This workflow ensures that the services used in freight cost calculation is also stored on the quote/order ant later used on the consignment.
A new action on consignment to open a list of web service communication log entries for the consignment.
A new action on consignment to download consignment events from Logtrade and open the events in a list.
Texts and instructions based on standard text rules were not inserted as source document texts and instructions.
Gross Weight and Volume are now calculated based on the Item Unit of Measure values for Weight and Cubage (if those values are specified on the Item Unit of Measure).

Obsoleted objects:

Table Service Rule2

23.2.228.0 (2024-03-13)

Non-inventory cost items did not update source document properly for locations with bin code mandatory.

23.1.226.0 (2024-03-07)

Removing a manually package from a consignment (remove from or delete) did not update/remove cost and dangerous goods and did not update the validation status of the consignment line (for comtinius labelling).
The error message "The neccessary consignments has alreday been created" has been amended with further instructions.

23.0.224.0 (2024-03-01)

Support for Sort Code, Budbee Order ID and Budbee Token as new fields on Sales Header.
Errors generated internally in BC during validation of delivery data on sales order did not set the validation status to Failed.
Services specified on source document was not respected when creating consignment(s) from warehouse shipment/-pick.
It was not possible to fetch items from source document if the consignment was created from a warehouse shipment.

Business Central 20 to 23.2

20.42.0.0 (2024-09-11)

This version is on par with 23.25.284.0 except for some features around posted service shipments and the possibility to automatically create a consignment when a warehouse shipment is created.

20.41.0.0 (2024-04-03)

This version is onprem only and on par with 23.5.235.0

20.40.221.0 (2024-02-21)

Items with type Non-Inventory are no longer inserted on warehouse shipment for locations that require bin codes.
Freight Payer, Freight Payer Customer No., Note of Goods and Goods Type Code are now transferred from Sales Order to Sales Shipment and used when creating a consignment from the shipment.
Goods Type Code specified on Sales Order was not always respected when creating consignment package line.

20.39.218.0 (2024-02-12)

Consignment created with Tasklet did not include items from linked source documents.

20.38.216.0 (2024-02-09)

Manifest ID was copied when using Copy Consignment.
Items with type Non-Inventory are no longer inserted on warehouse pick for locations that require bin codes.
When disabling automatic printing there was no printout when selecting Confirm and Print on a consignment.

20.37.214.0 (2024-01-24)

It was not possible to enter Logtrade License No. in setup without read permission for the delivery setup in all companies.
Wrong environment name was displayed under the API section in the Delivery Setup.
It was nto possible to use AddToConsignment from a package after version 20.34.204.0

20.36.212.0 (2024-01-10)

It was not possible to automatically create consignments with a rule with Event = "On After Shipment Posting" in combination with warehouse shipment posting.
It was not possible to create a consignment for a transfer order that had lines without item no.
Translations for cost codes.

20.35.210.0 (2024-01-09)

Services added in Qpick was not respected if UseQpickServices was not specified when calling the API.
A new overload for the procedure Package.AddToConsignment has been introduced that creates consignment items based on package items (that can contain information on Lot No./Serial No). This overload can be used in integrations that create packages (such as Tasklet).

20.34.204.0 (2023-12-28)

Calculation of item quantities, weight and volume was incorrect when using Inventory pick in combination with a location requiring bin code.
The implementation of Goods Type and Goods Type Code was inconsistent and has changed to use Goods Type Code in all situations.
No. of EUR Pallets has been removed from Warehouse Pick and Inventory Pick (has never been used in the application logic).
A Package Type Code specifies on a pick document are now used when creating a package for the pick document.
A consignment created from a package that originates from a pick document will now inherit Goods Type Code, Goods Marking and Shipment Template Code (if specified) from the Pick Document.

20.33.202.0 (2023-12-21)

Prefix and suffix has been added to Field Mappings.
Reference were cleared when changing address source manually on a Consignment Address.

20.32.198.0 (2023-12-13)

It was not possible to manually delete a package with item lines.
Qty. to Package were calculated on the Take line in a warehouse pick when using directed pick. This has been changed so the quantity to package is calculated on the Place line.
Quantites for consignment items were calculated on the Take line in a warehouse pick when using directed pick. This resulted on wrong quantities when selling in other unit of meausers than base unit of measure. This has been corrected so the calculation is based on the Place line.
Qty. to packaged was initiated with a value even if the warehouse pick were created with "Do not fill in Qty. to Handle" = true.
The functionality to specify "From Consignment Weight" in Service Rules has been rolled back since Logtrade TA adds required services for heavy packages automatically.

20.31.194.0 (2023-12-11)

It was not possible to install the app because of an data upgrade error

20.30.192.0 (2023-12-11)

Extra Reference added to field mappings.
Permission sets stored as data has been converted to permission set objects.
New field on Sales Header, Sales Shipment Header and Consignment: "Availability Token". Used by Instabox.
Extra Reference and Shipment Template Code has been added to Sales Shipment Header.
Currency Code in Freight Charge Discount Rules.
Swedish translations for Shipping Agent Service code updated.
"From Consignment Weight" in Service Rules that enables automatic creation of consignment services when a consignment is heavier that the declared weight on the rule.
It was not possible to post a service shipment if the service order had services, instructions or texts.

Note

If permission sets included in Logtrade Connect has been included in other permission sets, these inclusions needs to be reentered after app upgrade.

20.29.190.0 (2023-11-23)

Consignments created automatically after shipment posting did not always pickup the services that were specifies on the source document.
Enhancements and corrections in procedures for instructions, texts and services.
Quantity to Package were calculated also for other Warehouse Activity Types than Pick and Invnt. Pick.
Labels and documents for an automatically created return consignment are now printed when a consignment is manually printed.
New field on Consignment "Extra Reference".

20.28.187.0 (2023-11-17)

It was not possible to register a warehouse pick against an assembly order if there was a consignment creation rule set to trigger on registration of a distribution warehouse pick.
It was not possible to release a sales order with no outstanding quantity if there was a validation rule setup to trigger on sales order release.

20.27.184.0 (2023-11-13)

Copying a released consignment created the double quantity of packages.

20.26.183.0 (2023-11-09)

Source Document Instructions and texts wasn't transferred to posted documents.
The Qpick API now accepts package number when creating a consignment line.

20.25.181.0 (2023-10-26)

There was a transferfield error when using custom address as address source for a consignment address.

20.24.179.0 (2023-10-23)

Permissions for the tracking push AAD App was not created correctly.
Package weight are now only transferred to Tasklet Mobile WMS if weight type on package type is "Goods Included".
Unit codes transferred to Tasklet Mobile WMS did not respect settings for internal measure unt in delivery setup.
When creating packages from Tasklet Mobile WMS, any existing automatically crerated packages are now deleted.
Changes in a subscription for OnAfterCreateItemLines were not saved.
Delivery validation of sales order now use Outstanding Quantity.
Delivery validation of sales order required Shipping Agent Code/-Service Code to be specified. This has been changed so that default Shipping Agent/-Service Code are used if not specified on the sales order.
Source Document Services and Instructions was not deleted for Sales Order and Service Order when batch reports for deletion (after combined invoicing) was executed.
Field length for EUR Pallet Customer No. has been increased to 20 characters.
If Customs Invoice Grouping is not specified on Country/Region "Tariff No." will be used as default.

20.23.176.0 (2023-09-28)

Permissions for the tracking push AAD App was not created correctly.
The volume sent to Logtrade was wrong when using any other internal measure unit than Meter.
Assembly consumptions lines on warehouse pick are now converted back to the number of assembled items they represent and the assembled items are used on consignment and packages.
Items were not created on consignment when creation a consignment from a package that was created from a warehouse shipment or inventory pick.

20.22.174.0 (2023-09-25)

Changes in linking source documents:
- Weight and volume in the list of linked source documents and the list for selecting linked source documents to help the user select appropriate documents to link.
- Delivery date in the list for selecting linked source documents. Actual for posted shipments and calculated for orders.
- Multi select source documents to link.
- Selection list filtered on location code
Sending a split consignment for release did release linked "split childs" even if there was a validation error on the "split mother".
The Qpick API has been updated to support length, width, height and circumference on package lines.
Currency factor was not set when creating a consignment with source type Customer (affecting price calculations on customs invoice).

20.21.166.0 (2023-09-06)

There could be an error message about duplicate consignments when fetching status for consignments from Logtrade.

20.20.162.0 (2023-09-06)

Parameters on services linked to sales orders are now updated when a shipping agent service is specified.
Services can be specified on sales order without specifying shippning agent service code even if there's no service relation without shipping agent service code. When the shipping agent service code is specified, the service parameters will be updated if the service code has rerelation matching the shipping agent service code. If the specified shipping agent service code does not support any of the services linked to the sales order an error is thrown.
Bin code was not updated on inventory pick line for automatically inserted freight charge.
Custom data fields for customs invoice.
Custom data fields for delivery note.
A new XML-element in the web service for Qpick "UseQpickServices" that enables insertion and deletion of services in qpick.
The web service method in the Qpick API for retrieving consignment defaults now calculates services based on the shipping agent and shipping agent service code used in Qpick.
IMDG Flaming point now must be possible to interpret as an integer or decimal value in the dangerous goods table.
DB Schenker PartLoad has been added to the default package type relations
It was not possible to create a warehouse pick if any of the included source documents had a blank shipment date.

20.19.158.0 (2023-06-14)

Automatically added costs and freight did not work with directed put-away and pick.
Automatically added costs and freight did not work with locations with mandatory bin but without directed put-away and pick.
There was an error when registering a sales order if Logtrade Connect wasn't setup in the company.
Changes for compability with the Tasklet Logtrade Connect connecting app.
The Qpick SOAP webservice registered itself as LogtradeWs instead of LogTradeWs. We have now changed back to LogTradeWs.

20.18.156.0 (2023-05-31)

Automatic creation of text lines based on source document items did not work after version 20.12.70.0
It was possible to defined field mappings to a couple of flow fields on consignment header.
Deleting a consignment package line did not delete item lines on the packages.
Changing ship-to address code on a consignment did not update location code.
It was not possible to calculate freight on a sales order where all lines had 100% line discount.

20.17.154.0 (2023-04-24)

Adjustments in the logic for weight/volume calculations on package item lines.

20.16.150.0 (2023-04-18)

Validating Item No. on a package item line that was created based on a source document line replaced weight and volume and lost the reference to the source document line.
It is no longer possible to change Item No., Description or Unit of Measure Code on a package item line that is created based on source document number.
Deleting a cost code deleted rules for all cost codes.
It is no longer possible to create cost calculation rules if the value base has not been set on the cost code
It was not possible to manually delete a package that had created a cost if it was the last package on the consignment package line.
There was an error if a package was created from a consignment, anything changed on the package and then selecting Cancel in the create package dialogue.
Releasing a consignment created from Tasklet Pack & Ship raised an error if the Ship-to Customer Name was longer than 50 characters
It was not possible to setup EUR Pallet Customer No. without a Customer No.

20.15.147.0 (2023-03-24)

Item translations in customs invoice did not work properly.

20.14.139.0 (2023-03-24)

Adding/removing a consignment address of type Freight Payer now maintains the Payer and Paying Customer No. field on the consignment without having to use a separate Shipment Method with Payer = Other.
Functionality for tradeunits and sensors added to support Logtrade Connected Goods.
Copying an environment to sandbox did not set test mode in delivery setup and on shipping agent services.
Linking source documents by using the action "Link Source Document" on a consignment did not respect a changed matching option on ship-to address.
The message "Consignment No. '' does not exist" could in some situations be thrown when inserting a new consignment line.

20.13.88.0 (2023-03-14)

Item translations did not work in customs invoice when specifying a language code for customs invoice on country/region.
Test mode can be specified on individual shipping agent services.
Creating consignment from a source document with several location codes resulted in wrong items on the consignment.
It was not possible to copy a consignment from a released consignment.

20.12.70.0 (2023-02-22)

Barcode data on SSCC-label was incorrectly formatted so scanning could not interpret individual parts of information in the barcode.
A check that item GTIN is 14 characters long when printing SSCC-label.
Refactoring of instructions and free texts which has been separated into separate tables and been given a more consistent user interface.
- Manually edited instructions and free texts from linked source documents are now copied to the instructions and texts of the main consignment.
- New options for free text on customers and source documents that makes it possible to define free texts for customs invoice and delivery note on customers/vendors etc and source documents.
- Free texts for delivery note did not work.
- Settings in delivery setup that controls if manually edited free texts and instructions on a source document shall be inserted on consignments where the source document is used as a linked source document.
A new setting in delivery setup that decides if the logic introduced in version 20.8.45.0 that includes customer report selection in the calculation of delivery email shall be active or not.
BC API URL shown in delivery setup was not correct for production environments.
The setting on shipping agent service to ignore freight cost calculation errors did not work as expected.
Creating consignments from warehouse shipment and automatically attaching packages created from pick now also support multi shipment picks as long as the package only contains lines from the shipment the consignments are created from.
An existing carrier product in BC that is no longer valid in Logtrade caused the update of carriers and products from Logtrade to fail.
The list of available source documents to add as linked source documents did not respect modified linking criterias applied in the Linked Document Field Management codeunit.

Please note that there are several obsoleted objects in this release:

LTCConsInstruction.Table.al
LTCConsInstructionCreateXML.Codeunit.al
LTCConsHeadCustInvNode.Codeunit.al
LTCConsTextCreateXML.Codeunit.al
LTCConsignmentText.Table.al
LTCReleasedConsInstr.Table.al
LTCReleasedConsignmentText.Table.al
LTCEmailHelperBC19.Codeunit.al
LTCSourceInstructionLine.Table.al
LTCSourceDocInstructionLine.Table.al

Please make sure to test apps with dependencies on Logtrade Connect and change any references to the objects above. Make sure to do this before the rollout of 2023 Release Wave 1.

20.11.67.0 (2023-01-17)

Settings that decide if weight and volume shall be calculated or not were not respected when items were inserted on packages.

20.10.57.0 (2023-01-16)

There was an error when releasing a consignment with a package that contained an item line with a description longer than 50 characters.
Volume and weight was lost on package item line if unit of measure code was changed before quantity was specified.
Consignment cost were not copied to a credit memo when using the copy document function.

20.9.56.0 (2022-12-22)

There was an error when changing length, width or height on a consignment package line and afterwards leaving the consignment package line.
Releasing a prepared consignment using the release function on the consignment did not trigger a booking when a booking rule was setup for release.
Back order was not set automatically on consignment.
Dangerous goods lines did not get weight and volume calculated on item weight/volume, only item dangerous goods weight/volume.
Description on customs invoice was truncated to 35 characters if item translation or grouping on item no was used.

20.8.48.0 (2022-12-13)

Inhouse shipping agent customer number only worked when source type was Location (bug introduced in version 27.8.43.0).

20.8.45.0 (2022-12-12)

E-mail from custom report selection of type shipping was not used when calculating ship-to email on sales order

20.8.43.0 (2022-12-09)

Service parameter values defined on a source document for Logtrade generic services was not respected when the consignment were created.
Default service parameter value was restricted to 30 characters. The field length has been increased to 250 characters.
It was not possible to release a consignment with an item with a description longer than 35 characters.
Carrier Customer numbers defined on Location code did not work as intended.

20.7.24.0 (2022-12-06)

From this version the third part of the version number is the build number. Part one is the lowest BC version supported and position two is increased for each new release.

A warning is now shown if a Logtrade license are used in multiple companies.
Freight and costs were not inserted on zero amount sales orders.
Actions on consignment for tradeunits and asset associations has been hidden.
Packages created from warehouse pick with all lines from the same warehouse shipment are automatically linked to consignments created from the shipment.
Fetching status from job queue caused an error if split consignments was included in list of consignments involved.
Description on customs invoice lines now supports up to 70 characters.

20.6.0.1 (2022-11-17)

Permissions were missing for charge freight rounding rule

20.6.0.0 (2022-11-16)

New functionality:

A REST API for managing packages. Click here to learn more about the API.
Functionality for creating a configuration package for export/import of setup data.
Freight Charge Rounding Rules.
Specify free texts for customs invoice and delivery note on source (customer, vendor etc), source document and consignment.

Changes and bug fixes:

It was not possible to specify variant code on package item line.
In some situations it was not possible to enter a warehouse shipment number manually on a consignment.
Consignment item lines that has changed manually to zero quantity no longer prints on customs invoice or delivery note.
Delivery name is now set on location when installing the app.
When you create a Logtrade user from BC a notification is now shown warning about potential additional license costs.
We are now giving an early error message when trying to calculate freight cost on a fully prepayment invoiced order instead of just not inserting the freight cost line.

20.5.0.3

The permission group LTC USER was missing

20.5.0.2

Replaced zero values on customs invoice were not recalculated to the correct currency amount.

20.5.0.1

It was not possible to enter Source No. in warehouse pick when running on BC20.5

20.5.0.0

New functionality:

Rudimentary support for creating and sending tradeunits to Logtrade TA. Tradeunits is a vital part of Internet of Logistics and Connected Goods. Rudimentary = No logic for automatic creation of tradeunits in BC.
Support for creating and sending asset associations to Logtrade TA. Asset Associations is a part of Internet of Logistics and Connected Goods that gives the opportunity to live tracking of pallets and packages.

Changes and bug fixes

It was not possible to reopen a prepared consignment with a shipping agent service that had Reconfirm = New/Added Packages

20.4.0.0

Please note that we have moved the setting for package number generation from Shipping Agent Service to Package Type. This requires changes in setup if you are using SSCC or manual package numbers.

New functionality:

A framework for printing custom layouts defined in BC through Logtrade Integrated Printer. More info on this can be found here.
A rule table for automatic printing of custom report layouts on consignment prepare/release and package print.
Menu items for selecting and printing a custom report layout from package or consignment.
SSCC-label printing utilizing the framework and rules described above.
A Copy Relations function in the list of package type relations to make setup of new package types easier.
A new setting on shipping agent service: Ignore Freight Cost Calculation Errors which, if enabled, means that any errors during an automatic calculation of freight cost is ignored so the consignment can still be processed by Logtrade.
HS (harmonized system) code on item that is used when sending customs invoice data electronically.
MID (manufacturers identification) code on item that is used when sending customs invoice data electronically.
A new setting (Use Note of Goods) on shipping agent service that controls if note of goods shall be used on consignment package lines. The default value is true.
Agent Office can now be specified in address rules so the selection of agent can be automated when creating a consignment.
Create support email with request and response xml files attached from Logtrade web service communication log and the list of errors shown when errors occurs during validation/release of a consignment.
Create packages (including items) from inventory pick and warehouse pick. More info here.

Changes and bug fixes

The setting for package number assignment has been moved from Shipping Agent Service to Package Type.
SSCC-numbers on packages are now calculated automatically for packages created from, or linked to, consignments where shipping agent service that has Package No. Assignment = SSCC.
Manually created packages are no longer affected by change of shipping agent service with settings for automatic consignment package line creation or default package type. The manually created packages are left intact in such scenarios.
SSCC number are now calculated automatically when selecting package type on a package if the package type is setup for SSCC numbering.
Creating consignment from a package with no source document number or source number no longer warns the user for duplicates or asks for adding mot packages to the same recipient.
Zero value replacement on customs invoice did not multiply with qty. per unit of measure.
Scheduled update of consignment status from Logtrade using job queue in BC did not respect the update interval in the delivery setup.
Changing ship-to address code on a consignment did not update shipping agent and shipping agent service code based on the settings on the shipping address.
It was not possible to enter user id for quality control on a package.
Last Modified Date was not set on carrier when updating an existing carrier from Logtrade.
Rebranding from LogTrade to Logtrade in captions and tooltips.
Delivery Country/Region code in the service rule table makes it possible to control services by country even though ths same shipping agent service code is used.
A new event: "LTC ConsHeadCustInvNode".OnAfterBufferItemLinesSetConsItemLineFilter which gives control over which items that are used on customs invoice.
International name for dangerous goods was not sent to Logtrade.
Defining source document consignment services required shipping agent and shipping agent service code on the source document. This has been changed so that a service code can be inserted without knowing which shipping agent/-service code that will be used later. In this scenario it is not possible to defined service parameters from the source document, since the actual service name is not known in that stage.
It was not possible to send a consignment to Logtrade as saved with command = AddGoodsItems to make it ready to receive goodsitem lines later.

20.3.0.8

Changes and bug fixes:

A zero value unit price on a customs invoice line are now sent to Logtrade as 0.01 instead of 0.001 since Logtrade only prints two decimals on invoice lines.
Automatic costs were calculated when validating delivery data on sales order.

20.3.0.7

Changes and bug fixes:

The language of the document name of a shipment note now follows the same logic as other labels on the report: If recipient country code is 'SE" then 'Följesedel' will be printed, otherwise 'Shipment Note'.
When using clients with different settings for decimal digit, there could be conversion errors for decimals (typically in weight for limited dangerous goods).
LQ QTY and EQ QTY was not added to the description on international dangerous goods declarations.
The description of a unit of measure is now printed on delivery note instead of the unit of measure code. For international consignments a unit of measure translation for the language code ENU is used (if it exists).

20.3.0.6

Changes and bug fixes:

Delivery name on location are now used as ship-to name on sales return order and purchase order.
Ship-to Phone No. and Ship-to Email on sales return order are now populated from location.
Adding a linked source document that was part of another warehouse document than the consignment did not result in items being added to the consignment.
Consignment items were not created for sales return order where the location required receive.
Better support for country specific dangerous goods services.
Package type code, length, width, and height has been added to sales order validation rules.
The consignment duplicate check did not work as supposed when automatic archiving of released consignments was turned off.

20.3.0.5

Changes and bug fixes:

Volume was not calculated on consignment package line
The document name for delivery note is now in english if the language on the source document does not match default language code in the delivery setup.

20.3.0.4

Changes and bug fixes:

It was not possible to send a consignment directly for release and at the same time use Booking Method = On Release. This has been enabled so the consignment is sent as prepared, booked and then released.
New actions in the list of error messages so the user can view request/response directly in BC. Previously it was only possible to export to an xml filed.
Enhancements in the list that shows validations errors thrown by Logtrade.
Using Consignment Worksheet to prepare a consignment did not mark consignment package lines as prepared.
Variant Code has been added to package item lines.
New settings on shipping agent service "Limited Quantity Dangerous Goods" and "Excepted Quantity Dangerous Goods" that control if and when these types of dangerous goods shall be handled for the shipping agent service.
New setting on shipping agent service "Combine Limited Quantity Dangerous Goods" and "Combine Excepted Quantity Dangerous Goods" that control if these types of dangerous goods shall be combined with regular dangerous goods for the shipping agent service.
"LTD QTY" and "EX QTY" are now added to the description for limited quantity dangerous goods and excepted quantity dangerous goods when printing these types of dangerous goods on a dangerous goods declaration.

20.3.0.3

Changes and bug fixes:

Delivery Name on Location was not saved during app upgrade.

20.3.0.2

Changes and bug fixes:

Packaging volume was not calculated on consignment package line for package types with Volume Type = Goods Excluded. This error was introduced in version 20.1.0.0.
"Delivery Name" has been added to location so that "Name" can be used as an internal description while "Delivery Name" is used on consignments.
Consignment duplicate check was triggered when selecting agent office on sales order.
Dangerous goods were not created for consignment package line for a split consignment if "All Dangerous Goods on First PAckage" were enabled on the shipping agent service used on the consignment.

20.3.0.1

Changes and bug fixes:

It was not possible to print from the released consignment worksheet.
Shipping agent and shipping agent service was not fetched from transfer order and service order to warehouse activity header.
It was not possible to send automatic booking on release if the consignment was sent for release directly without first being prepared.
A new event has been added to the Consignment Worksheet page: OnAfterSetFilter. This event makes it possible to apply custom filtering in the journal.
Packages are no longer updated with weight when refreshing consignment items if there are one or more manually created packages on the consignment.
There was a duplicate error if multiple automatic costs where setup to be created for a consignment.

20.3.0.0

New functionality:

A new setting on shipping agent service "All Expected Dangerous Goods on First Package" that specifies that all expected dangerous goods shall be applied to the first package on a consignment. This option is applicable when using continuous labelling from inventory pick or warehouse pick and you want packages not containing dangerous goods to also have labels marked for dangerous goods. The expected quantity is based on the quantity field on the warehouse activity line.

Changes and bug fixes:

An automatically created cost that was delivered (or manually removed) on the source document was calculated and inserted again when updating anything on the consignment that triggers a calculation of costs.
A new setting on package "Separate Consignment Package Line" has been added that, if enabled, creates one (1) consignment package line for each package.
An empty consignment item line was inserted when fetching items from source document to consignment manually in the list of consignment items.
Consignment items were renumbered when refreshed from source document which caused issues when dealing with partial pick/delivery and dangerous goods.
Customer number in Shipping Agent Customer Numbers are no longer mandatory, meaning that you can setup only an EUR Pallet Customer number for a customer.
Internal Measure Unit in Delivery Setup now supports Centimeter and Millimeter.
Package length, width, height and circumference are nov available on sales order.

20.2.0.1

Changes and bug fixes:

The automatic installation of the AAD Application introduced in version 20.2.0.0 has been removed due to install/upgrade issues
A new action on the Delivery Setup page to configure the tracking AAD App
Automatic costs based on item values were deleted when a consignment was sent to Logtrade.

20.2.0.0

New functionality:

An AAD application is created automatically during install to which the user can give consent to approve that Logtrade can push tracking data to Business Central. This functionality is not ready on the Logtrade side yet, so this is a preparation for that.

Changes and bug fixes:

Changing from a shipping agent service with a local timetable to one without did not reset the timetable date/time field.
The permission group LTC USER was not created.
API URL and Tenant ID is visible in delivery setup when running on cloud. This is to make it easier to order the tracking push from Logtrade who will need this information.

20.1.0.1

Changes and bug fixes:

When creating consignment(s) from Warehouse Shipment or Warehouse Pick a consignment was not created for a source document if the first line for the source document had picked quantity = 0.
Deleting a cost code did not delete cost calculation rules.
There were issues when editing instructions linked to customer, vendor etc.
No. of packages on sales order validation rules were not used when validating a sales order against Logtrade.

20.1.0.0

New functionality:

A new setting on shipping agent service "Show Package Measures on Consignment Package Lines" that, if enabled, makes length, widht and height visible on consignment package line. Updating these values will calculate volume and update the underlying packages with the same dimensions.
A new calculated value has been added to Default Service Property Values: Outstanding Order Value.

Changes and bug fixes:

When creating consignments from warehouse shipment and warehouse pick, a consignment was not created if the source document was already used as source document on a consignment or linked to a consignment. Now only consignments that has never been sent to Logtrade are taken into consideration. Once a consignment has been sent to Logtrade it is now considered as "closed". There is an assumption made in this design that if you create consignment 2..n for a source document from a warehouse shipment/-pick, the warehouse shipment/-pick has been posted/registered after the previous consingment were created.
It was not possible to print from released consignment.
New events in the codeunit Warehouse Integration to allow more control of quantity calculations etc. (OnBeforeGetWarehouseQty, OnBeforeCalcWhseShipLineQty, OnBeforeCalcWhseActLineQty, OnBeforeWarehouseLineExist and OnBeforeGetSourceDocLineQty).
Creating a consignment using source type customer or vendor (without a source document) did not se terms of delivery location.
Creating a consignment from a customer or vendor card/list did not populate the location code on the consignment.
It was not possible to add a cost of type item (inventory) on a consignment created from a warehouse pick if the warehouse pick was fully registered (and thus deleted).
Creating consignments for jobs now support sell-to, ship-to and bill-to address information specified on the job.
If rules for automatic consignment creation existed, but non of the rules applied to the warehouse shipment/-pick you were posting, you got an error message saying that "All necessary consignments has already been created".
Creating a consignment linked to a customer (without source document) did not use the Ship-to Code on the customer card.
Fetching e-mail address from customer will now prioritize an e-mail address specified on a custom report layout with usage = S-Shipment over the e-mail address on the customer card.
Language code on contact was not used to set consignment address e-mail language.
It was not possible to create a consignment from an inventory pick if the pick source document was a job.

20.0.0.0

This version is identical with 19.5.0.0 but compatible with BC20.

Business Central 19

19.9.0.0

Back Order was not calculated automatically on consignments.

19.8.0.0

This is a feature/fix rollup comparable with version 20.5.0.3 except functionality dependent on functionality in the base app not present in BC19.

19.7.0.2

This version is a contains changes up to version 20.3.0.7

19.7.0.1

This version is a contains changes up to version 20.3.0.6

19.7.0.0

This version is a contains changes up to version 20.3.0.5

19.6.0.0

This version is a contains changes up to version 20.3.0.1 that are compatible with BC 19.

Changes not included are:

Inventory pick for job
Sell-to/Ship-to on job

19.5.0.0

Please pay extra attention to the changes in archiving of released consignments in this version. The automatic archiving of consignments is a costly process from a database perspective, and in high volume scenarios it can be a good thing to schedule archiving to off hours.

New functionality:

Locally defined timetables (with lead time in days) are now used to calculate lead time on sales orders.
Deleting a released consignment now sends an archive request to Logtrade.
A new field on Logtrade User called Override Consignment Print Queue that, if enabled, will use the print queue specified on the user instead of the print queue on the consignment.
The field "Automatic Archiving of Released Consignments" has been added to the delivery setup that controls if released consignments shall be archived automatically.
Codeunit (12063949) that can be used from the job queue to archive released consignments.
The action "Archive Released Consignments" has been added to the consignment worksheet.
XML request and response in the Logtrade Web Service Communication Log can now be viewed directly in BC without having to export to a file.

Changes and bug fixes:

Migrating data into SaaS could cause duplicate ID errors when releasing consignments after migration.
Duplicate fields on item card för weight and volume has been removed.
Tracking pushed from Logtrade did not update released consignment if tracking number was a package number.
Customer Eori number are now synced with default address identifier.
Company Eori number are now synced with default address identifier.
Deleting a prepared consignment manually sent two archive requests to Logtrade.
It was not possible to edit a datetime service parameter value that had already been converted to XML format.
If a consignment exists when posting a sales shipment, but the consignment has not been sent to Logtrade as prepared or released, the sales shipment (instead of the sales order) will be updated when the consignment is sent to Logtrade.
Dangerous goods were not calculated automatically when adding a package to a consignment by using the AddToConsignment function on a package.
Language code NOR has been removed as Email Language on consignment address.
If consignment shipment date is based on source document shipment date, source documents with different shipment dates are no longer linked to the same consignment when creating consignments from warehouse shipment or warehouse pick.
The change status term Archive has been changed to Delete since that is what happens in Business Central. If a consignment has been sent to Logtrade an archive request will be sent to Logtrade.
The consignment worksheet can now be used also to delete consignments that has not been sent to Logtrade.

19.4.0.1

New functionality

We have started to add links to contextual help on many pages and are in the process of writing help texts on this site. This is a work in progress.

Changes and bug fixes:

The tracking API that receives status tracking from Logtrade now accepts consignmentId. This means, that even if the carrier sends package number as tracking number, the tracking entries will be correctly linked to a consignment.
Adding a manually created package to a consignment now supports redirection to consolidated consignment i multiple consolidation levels.
Delivery Terms Location are now truncated to 17 characters.
It is no longer possible to delete a sender address code that is used on a Logtrade user or an address rule.

19.4.0.0

New functionality

Custom data captions can now be defined in the list of Custom Data Captions.

Changes and bug fixes:

Rounding of quantity in customs invoiced changed the line amount.
The copy consignment function did not update the consignment with contact email, phone and mobile phone if the user selected to swap delivery and pick address.
Automatic assignment of SSCC package numbers, and test for manual package numbers, for packages created automatically from consignment did not work.
Automatic freight cost calculation was triggered when payer was Recipient or Other. Freight cost calculation now only occurs when payer is Sender.
It was not possible to create consignments automatically from a warehouse shipment/-pick if there, on the source documents, were a mix of shipping agents/-services that should have consignments created and some not.
If you try to add a package to a consolidated consignment the package will automatically be added to the consolidation consignment, package line will have a Consolidated From No. and aggregation of packages will occur for packages with the same package type and Consolidated From Consignment No.

19.3.0.5

Changes and bug fixes:

Using warehouse shipment date as shipment date on consignments did not work for pick lines with type assembly order.
The setting for warehouse quantity calculation was not fully respected in all situations when creating consignments from warehouse picks.
Specifying service rules from e.g. a customer did not automatically populate the customer number as source number.
Consignments sent to Logtrade that are automatically created on release of a source document are no longer deleted when reopening the source document.
Changing sipping agent service on a consignment now respects manually edited/created services on a source document and also creates new default services for the chosen shipping agent service (as it would have happened on the source document).
It was not possible to use limited dangerous goods with decimals in gross weight.
Decimals in no of dangerous goods packages are now rounded upwards to nearest integer.
Creating consignments multiple times from the same warehouse pick could create to many consignments.
Package.AddToConsignment() now links the package to the consolidation consignment if the consignment for the source document has been consolidated.
If a source document has more than one consignment, Package.AddToConsignment() will now select the last consignment.
A new event "LTC ConsHeadDeliveryNoteNode".OnAfterCreateDeliveryNoteItems that allows modifications of delivery note item data before it's being sent to Logtrade

19.3.0.4

Changes and bug fixes:

Changes in delivery date calculation introduced in 19.3.0.3.

19.3.0.3

Changes and bug fixes:

Delivery date on consignment could not be based on warehouse shipment's shipment date.

19.3.0.2

Changes and bug fixes:

The procedure Package.PrintDeliveryLabel has got a new overlay procedure which makes it possible to decide if consolidation messages shall be shown and the possibility to specify print queue.
Automatic booking based on booking rules in BC was triggered also for consolidated consignments.
Booking triggered by booking rules did not not update booking status on consignments.
Items with type = service were not copied to consignment items.
A new action has been added to the consignment page that opens the consignment (or rather a consignment list) in the Logtrade GUI.
Batch release from job queue gave an error if there were no consignments to release.
A new setting in the delivery setup controls if package tracking number shall be cleared after posting delivery or not.
Consignments created in test mode can now have a prefix to the consignment number specified on the delivery setup, to avoid colliding consignment numbers in Logtrade.
Name and e-mail are now defaulted from the specified BC user when adding a Logtrade user from within BC.
Instructions can now be specified also for ship-to addresses.
It was possible to use non limited dangerous goods declared item with a limited dangerous goods service.

19.3.0.1

Changes and bug fixes:

It was not possible to manually specify package no. on a package that wasn't linked to a consignment.
The delivery role center has been updated
Actions for tracking from posted sales shipment is no longer replaces with Logtrade tracking if Logtrade Connect is not configured in the company.
It was not possible to open pick documents if Logtrade Connect was not configured in the company.
The setting for how item quantities shall be calculated when creating consignment from warehouse shipment has been extended so it also applies to consignments created from pick documents.
Creating a consignment for a customer or vendor and selecting a ship-to address could lead to contact information being cleared.
Context sensitive help has been changed to https://connect.Logtrade.se/bc/docs.
Context sensitive text has been added to consignment (as a first step).
Help in assisted setup has been redirected to http://connect.Logtrade.se/bc/docs/walkthrough/assisted_setup.html.
The help movie in assisted setup did not work.
Validation of sales order or consignment did not work if the shipping agent service was setup with Reconfirm Consignment = Add/Remove Packages
A new option value has been created for Reconfirm Consignment on Shipping Agent Service: "Replace consignment (keep tracking information)", to enable resending to Logtrade with new packages without renumbering existing packages.

19.3.0.0

New functionality:

Select Agent Office ID directly on Sales Order
Integration with Online Maps from selection of agent office, consignment address and released consignment address

Changes and bug fixes:

Services defined on source document was not respected if there where default services specified
Dangerous goods lines were not created when linking split shipments if the package line already had been created on the “split shipment mother consignment”.

19.2.0.5

Changes and bug fixes:

Permissions were missing for Source Document Service tables.
Datatypes were missing for default service parameter values created when using Assisted Setup.

19.2.0.4

Changes and bug fixes:

It was not possible to fetch items to a consolidation consignment.

19.2.0.3

Changes and bug fixes:

Field mappings from Job did not work.
It was not possible to add a package to a validated consignment even though “Reconfirm Consignment” on the shipping agent service was set.
Items of type “Service” are now included in the items for a consignment which means they are included in i.e. amount calculations.
Packaging weight and volume on consignment line was not calculated in all situations.
Changing post code did not trigger recalculation of city.
Lot No., Serial No. and Expiration Date are now printed in the internal package label.

19.2.0.2

Changes and bug fixes:

Inserting a consignment package line with no default package type code on the shipping agent service code raised an error about package type.

19.2.0.1

Changes and bug fixes:

Barcodes for internal package labels now print the internal ID as a barcode (Code-39, Codabar, Code-128 or Code-93)

19.2.0.0

New functionality

Consignment Services are now fetched to the source document where parameter values can be specified. When creating a consignment, the services are created based on what has been specified on the source document.
A new instruction type “Internal” which is not sent to Logtrade and shown on the consignment, both as a fact box listpart and as que icon “Number of Internal Instructions”. Internal instructions can (as other instructions) be set on the customer and these are copied to the source document (e.g. sales order) where they can be edited and finally copied to the consignment.

Changes and bug fixes:

Order value and delivery value as consignment service parameter values now includes VAT.
Instructions of type “Free Text” on a source or source document are now copied to a consignment’s free texts.
Only the first extra text line was inserted as free text when manually specifying a standard text code as consignment free text.
Using both standard texts and instructions linked to e.g. a customer deleted the instructions created from standard texts.
It was not possible to create consignment from a package with a source document type/-No.

Known issues:

Barcodes on internal packages labels do not work.

19.1.0.0

New functionality

Internal package labels are now printed with a barcode when using Business Central in Cloud. Barcode symbology can be setup on package types.

Changes and bug fixes:

It was not possible to use value based automatic cost with source document values as calculation base.
It was not possible to release a sales order where delivery validation had failed if the delivery validation rule was deleted.
It was not possible to create consignment from customer card, vendor card etc. if a default source document type was set in the delivery setup.
A menu item for cost codes were missing in the delivery role center.
Default services was not created for consignments when using a default shipping agent.
Decimal values in service parameters were sent to Logtrade with a wrong decimal symbol.
The source code is now included in symbols.
When validating delivery data on sales order when GuiAllowed = false any errors generated internally in BC (i.e., not by Logtrade validation) did not set delivery validation = failed.
Running assisted setup as a delegated admin raised a permission error on Retention Policy Setup. If permissions are missing the policy is no longer created and can instead be created manually from an action on the delivery setup page.

19.0.0.0

Changes and bug fixes:

Trying to create consignment(s) from warehouse pick where no lines had “Qty. to Handle” threw an error message that didn’t describe the actual error.
The assisted setup has been simplified by removing the page for mapping between shipment methods and delivery terms.
Customs invoice rounding with quantity in description could lead to a spill/overflow.
Using Sales Header as a temporary table raised an error when Ship-to Phone (and other fields) was populated.
When changing package dimensions for a package type with “Volume Type” = “Goods included” the package volume is now updated.
Consignment No. has been added to the list of Logtrade Webservice Messages and is populated for all webservice calls to Logtrade that applies to one single consignment.
Validation error messages are now started with “Logtrade returned the following errors:”.
It was not possible to turn off “Automatic Printing” in the delivery setup and use “Confirm and Print” on a consignment.
The copy consignment function created duplicate packages.
If you copied a consignment and selected any of the address replacement options and after that changed e.g., shipping agent service, the addresses were created based on default address rules. Now the replacement options selected when copying the consignment are stored on the consignment and respected when addresses are recalculated.
Calculating freight cost from sales order and inserting the freight cost now respects the Prepayment % that is set on the sales order. Any other method of updating a source document with freight cost still does not use prepayment since that update can take place during posting of delivery with an auto insertion of the sales order at posting time.
A menu item for sales order validation rules were missing in the delivery role center.
Support for specifying datetime service parameter values has been added.
Adding a package manually to consignment did not work when the source document number on the package was a linked source document number to a consignment.
The delivery tab on sales order has been reorganized.
Consignment addresses based on customer or vendor did not have a VAT Registration No.
Using Shipment Template Rules resulted in an endless recursion loop.

New functionality

Print delivery label from a single package.
Shipment Template can now be specified on sales order, inventory pick, warehouse pick and Checkout Method.
The new mail-functionality introduced in BC17 instead of the old SMTP-mail is now used from the two e-mailing functions on consignment.

Business Central 17 and 18

17.7.0.1

Barcodes on SSCC-label were not formatted correctly
Weight and volume was not calculated on package item line if unit of measure code were validated before quantity.

17.7.0.0

This is a feature/fix rollup comparable with version 20.5.0.3 except functionality dependent on functionality in the base app not present in BC17.

17.6.0.0

This is a feature/fix rollup comparable with version 19.4.0.1 except functionality dependent on functionality in the base app not present in BC17 (mainly new e-mail experience and bar codes on internal package labels).

17.5.0.0

Changes and bug fixes:

Ship-to e-mail address on sales order was limited to 20 characters when fetching from ship-to address.
When updating carriers from Logtrade all carriers always got the date/time for last update changed even if there were no change or only one carrier was updated.
A prefix in the Default Service Property Value table replaced the property value instead of prefixing it.
Print a package label from the package line did not work if the consignment didn’t have status = Prepared.
A personal Logtrade user is no longer needed in test mode or when only validating delivery data from a sales order.
Errors when preparing a consignment using the Qpick API did not return error messages.
Goods type was not assigned automatically on consignment lines in some situations.
It was not possible to use a package type on an inventory pick if the package type had a cost code.
Columns with tracking information in the list of released consignments are now only shown if tracking is pushed to BC.
Carrier Customer No. was not calculated for a consignment address with sender address as source.
Source Type and Customer No. is now mandatory in the Shipping Agent Customer No. list.

New functionality

New fields on shipping agent service for specifying unit price rounding precision on customs invoice lines and what action to take when rounding is needed.

17.4.0.1

Changes and bug fixes:

It was not possible to create sales order from custom card/-list.

17.4.0.0

New functionality

“Default for Consignments” on Shipping Agent and Shipping Agent Service code which selects the Shipping Agent/-Service Code if that value could not be calculated any other way.
A new locking mechanism for batch creation/sending of consignments has been introduced to meet the requirements of high-volume usage scenarios. This functionality can be enabled in the Delivery Setup.
Identifiers can be defined for consignments, packages, and consignment addresses. These identifiers can serv a multitude of purposes such as EORI-numbers for consignment addresses, Internet of Logistics-ID:s etc.

Changes and bug fixes:

A new setting in Delivery Setup “Link Warehouse Source Documents” can be turned of to completely disable the automatic linking of source documents when consignments are created from warehouse shipment or warehouse pick.
Stability- and performance improvements in the functionality for Consignment Validation introduced in version 17.2.0.0.
Price Quote errors during batch creation of consignments prompted each individual error to the user.
Tooltips on Shipping Agent Service fields.
It was not possible to use delivery address customer numbers when a different bill-to customer number was used on a source document.
The Assisted Setup showed Shipping Agent Services for Shipping Agents that was not linked to a Logtrade Carrier.
Error messages when sending a consignment to Logtrade are shown as a message box if it is one single item instead of always as a list.
It was not possible to setup address rules that generated carrier customer number on address type “Custom Fees Payer”
Carrier customer number was not calculated for address based on custom addresses.
Ship-to phone,-e-mail and -mobile phone no was not populated on sales order if Customer number was the first field on the sales order (i.e. the field “No.” was hidden because of one single number-serie).
Automatic validation of delivery information on order are now only triggered by manual release of sales order, not automatic releases from e.g. delivery, invoicing etc.,
Sending consignments with Confirm Status = Prepare to Logtrade from the consignment journal showed error messages for each consignment that had errors. These error messages are now suppressed.
Sending consignments with Confirm Status = Prepare to Logtrade from the consignment journal resulted in the message “There are no consignments to process”.

17.3.0.0

New functionality

A new event in Rules for Automatic Consignment Creation: “Post Warehouse Shipment”. The existing “Post Shipment” does no longer trigger for shipments created from warehouse shipment posting.
Country Code has been added as a criteria in the Confirm Status Rule table.
Support for retention policies for Logtrade Web Service Communication Log Entries.

Changes and bug fixes:

Price Quote and TimeTable was triggered by validation.
Events has been added to code for automatic consignments for enhanced control of logic.
Changing status on consignments from Consignment Worksheet could in some situations send an empty list of consignments to Logtrade resulting in the error “Criteria cannot be empty”.
“Message Entries” has been renamed to “Logtrade Web Service Communication Log Entries”.
The automatic creation of consignments on release of sales order has been moved from the event OnBeforeReleaseSalesDoc to OnBeforeManualReleaseSalesDoc to prevent the consignment creation to be triggered by automatic reopen/release during posting of documents. The corresponding change has been made to purchase documents. This means that only manual release from the order will create a consignment.
Automatic creation of consignment on release of service order was not triggered.
Validation of delivery data on release of sales order is now only triggered if validation status <> Approved. When reopening a sales order, the validation status is cleared. Previously the validation was triggered also when e.g. posting of inventory pick needed to reopen/release the order to update it.

17.2.0.0

New functionality

Consignment Validation; Makes it possible to verify that the data on the consignment is correct without preparing or releasing the consignment
Delivery Validation on Sales Order; Makes it possible to verify that the order is OK for a consignment
Sales Order Delivery Validation Rules; Makes it possible to automatically validate that the order is OK for a consignment and block the release if not successful.
Mobile Phone Number on Ship-to Address.

Changes and bug fixes:

Agent Office ID was not used when creating a consignment for a sales shipment with an Agent Office ID.
Package Type Code has been extended to 20 characters.
Field lengths in many fields (such as name fields) has been adjusted to align with field lengths in standard BC.
No. of Packages in Dangerous goods lines generated on a consignment was not rounded to zero decimals.
Consignment did not open automatically when specifying so on Rules for Automatic Consignment Creation.
Ship-to Phone/-Mobile Phone and -E-mail are now copied from sales order to sales shipment for use on consignment created from sales shipment.
Print Queue was not set correctly when specified on Location.

17.1.0.1

Changes and bug fixes:

It was not possible to register a warehouse receipt if an automation rule for creating consignments on registering warehouse picks was defined.

17.1.0.0

New functionality:

Consignment instructions can be registered linked to customers, vendors etc. These instructions act as default instructions copied to source document where they can be edited and finally copied to the consignment when that is created.
Checkout options can be setup in a table together with Shipping Agent Code and Shipping Agent Service Code. By validating Checkout Method Code on a sales order, the Shipping Agent Code and Shipping Agent Service Code is fetched from the Checkout Method. This functionality is targeted to web shop integrations.

Changes and bug fixes:

Unit Price on Customs Invoice Line is rounded to three decimals.
It was not possible to release a consignment if a package had been created by a user with a User-ID longer than 30 characters.
When registering pick for multiple orders and using consignment automation only one consignment was created.
When creating consignments for multiple source documents using automatic consignments, source documents were not linked.
Mobile Phone No. on Customer and Vendor is now used as Ship-to Mobile Phone No on Sales Order and when Consignment Addresses are created.
When creating consignments from Warehouse Shipment/-pick the fields different values in the fields Name and Address did not trigger a separate consignment.
The action “Create and Print Consignments” has been added to Warehouse Shipment.
Enhanced error handling when using automatic creation and validation of consignments when registering Warehouse Pick.
The list of created consignments from Warehouse Shipment-/pick are no longer opened if “Create & Print” was selected and there where no errors during validation with Logtrade.
Weight and volume are now updated on consignment line when adding linked document(s) if there are one (1) single consignment line.
Logtrade Connect is now available in Norway (with English language).
It was not possible to create consignment(s) for service order from a warehouse shipment.
Tracking information was not correctly saved on released consignment.
Customs invoice line grouping on Country/Region are now initiated with “Tariff No.” during setup (this does not apply to EU countries if the company information has a country code that is an EU country).
Calculation of number of items was wrong when creating consignment from a warehouse pick in a location using directed pick.
Number of Shipping agents are shown on Carriers and Number of Shipping Agent Services are shown on Carrier Products.

17.0.0.1

Changes and bug fixes:

Length, width, height, and volume was not recalculated on packages when changing package type code on a consignment line.
It was not possible to manually edit truncation rules.
Change of Note of Goods on Inventory Pick was not transferred to the consignment.
Change of Goods Type Code on sales order or inventory pick was not transferred to the consignment.
It is no longer possible to manually change Freight Payer on Sales Order and Sales Return Order (since this field is controlled by Shipment Method Code and it’s default payer.
Delivery fields on sales order that got values because of No. of Packages > 0 was not updated if No. of Packages was changed to zero and changes after that was done in fields that have impact on calculations of e.g. Sender Customer No.
Delivery fields related to weight and volume are no longer editable on sales order/-return order and inventory pick I No. of Packages are zero.

17.0.0.0

This version is based on 15.3.0.7

New functionality:

A role center that makes Logtrade Connect functionality visible in the Role Explorer

Changes and bug fixes:

The Delivery Setup page has been redesigned. Many menu items has been removed since they can be accessed by the Role Explorer (and the Manual Configuration list).

Business Central 15 and 16

15.3.0.11

Changes and bug fixes:

Changing status on consignments from Consignment Worksheet could in some situations send an empty list of consignments to Logtrade resulting in the error “Criteria cannot be empty”.
Codeunit 12063908 for schedule release of consignments has been changed so it only processes consignments with Shipment Date <= WorkDate.

15.3.0.10

Changes and bug fixes:

It was not possible to create consignment(s) for service order from a warehouse shipment.

15.3.0.9

New functionality

Consignment Instructions can be registered linked to a customer. These instructions are copied to sales order where they can be edited and finally when a consignment is created the instructions are used on the consignment.

Changes and bug fixes:

Unit Price on Customs Invoice Line are rounded with three decimals.

15.3.0.8

Changes and bug fixes:

Length, width, height, and volume was not recalculated on packages when changing package type code on a consignment line.
It was not possible to manually edit truncation rules.
Change of Note of Goods on Inventory Pick was not transferred to the consignment.
Change of Goods Type Code on sales order or inventory pick was not transferred to the consignment.
It is no longer possible to manually change Freight Payer on Sales Order and Sales Return Order (since this field is controlled by Shipment Method Code and it’s default payer.
Delivery fields on sales order that got values because of No. of Packages > 0 was not updated if No. of Packages was changed to zero and changes after that was done in fields that have impact on calculations of e.g. Sender Customer No.
Delivery fields related to weight and volume are no longer editable on sales order/-return order and inventory pick I No. of Packages are zero.

15.3.0.7

Changes and bug fixes:

It was not possible to create consignments with default delivery date based on the source documents delivery date

15.3.0.6

This is the last version which is fully synced with the BC14 version (14.3.0.6).

BC14 and BC15 will after this version be supported with critical bug fixes in line with the Microsoft Lifecycle Policy (October 2023 for BC14 and April 2021 for BC15).

Changes and bug fixes:

To many dangerous goods lines were created with certain setup scenarios.
Errors when creating and sending consignments automatically were sometimes not showed to the user.
Codeunit 12063908 has been added and can be scheduled in the Job Queue to perform automatic release of consignments. The parameter string can be used as filter for shipping agent.
Agent Office ID is now cleared when changing Shipping Agent Service Code on Sales Order or Consignment.
The Sea Transport Definition table has been extended with fields for specifying country code and post code intervals also for the sender party.
There was an error if a gate code longer than 10 characters were used on a sales order.
When searching for the delivery contact in the contact table a filter is now set on type=person.
A SOAP web service is for consignment creation etc. is now published automatically under the name LogtradeWs when the app is installed. The web service covers the functionality earlier described in the change log under the name Qpick. If you already have codeunit 12057609 setup as a webservice you might want to review the list of web services since you will get one more instance of this codeunit as a web service (this time for the specific tenant).

15.3.0.5

Changes and bug fixes:

It was not possible to change Logtrade License No. using a customer license.
Delivery date on released consignment used for follow-up in role center cues was not calculated correctly.
Dangerous goods calculations were not correct for sea transport.
A user can now confirm to link source documents manually even if fields such as name, address etc. does not match.
A developer can now with a subscribing procedure turn off matching on fields such as name, address etc. when source documents are linked to a consignment.
It was not possible to drilldown to property values for a released consignment service.
Consignment Item Lines was left in the table when a consignment was released.
It was not possible to create a quote for a contact that was not liked to a customer.
The field Agent Office ID on Sales Header had an invalid table relation.

15.3.0.4

Changes and bug fixes:

Goods Type Description was not populated when creating consignment from sales order and a Goods Type had been entered on the sales order.
Tracking number and package numbers are no longer reset when reopening a prepared consignment. Instead the reset takes place if the shipping agent service is changed.
It was not possible to create consignment from source document with an address setup using inhouse forwarder customer number.
Package volume was not calculated when manually entering length, width and height.

15.3.0.3

Changes and bug fixes:

The wrong encoding was used when exporting XML-requests from the message log.
Consignment Status reported back to Qpick has been changed to an integer value
The wrong page was opened when trying to open standard text rules from Delivery Setup.
It is now possible to enter country specific customs invoice declaration texts in the country/region table.

15.3.0.2

Changes and bug fixes:

An obsolete version of Logtrade’s ChangeShipmentStatus method was used in web service calls which could lead to unexpected results when changing status from the Consignment Worksheet.
Logtrade Connect fields are now visible on archived sales order.

15.3.0.1

Changes and bug fixes:

It was not possible to enter Unit Price on manually created consignment item lines.
It was not possible to copy a consignment if the target consignment was already inserted.
Consignment status was reported as an array in the Qpick API.
Last tracking event code and description are now visible in the list of released consignment and the worksheet for released consignments.
A new action on consignment to disconnect the consignment from a split consignment
A new checkbox “Connected” in the consignment selection list that is opened when connecting consignments to a split consignment.
Ship-to E-mail, Ship-to Mobile Phone No. and Ship-to Phone No. was emptied when changing Ship-to Contact even if the new Ship-to Contact did not match a contact for the sell-to customer.
Extended fields on Sales Header and Sales Line now exists in archive tables.

15.3.0.0

New functionality

Freight charge on source documents can be automatically recalculated during consolidation so that the source document of the consolidated consignment has no freight charge and the freight charge on the source document of the consolidation target consignment is based on the new cost of the consignment.

Changes and bug fixes:

Editing linked source documents by using drill down in the cue icon for linked source documents did not update the consignment items.
Consignment status is now reported back to Qpick as integer.
The Qpick web service method now also has PrintQueue as parameter.
Item prices in consignment was not calculated when creating consignment based on shipment created from posting with delivery only (not “ship & invoice”) and the order no longer existed.
Price and amount on consignment items are now shown (and edited) in their original currency.
The Swedish translation for “Shipping Agent Service Code” has been changed to “Speditörstjänst” in the BC15-version of the app.
It was not possible to select “Link Source Documents” on a consignment based on a shipment.
When consolidating, the consolidated consignment gets its freight cost cleared and the target consignment’s cost is recalculated. Both recalculations are done without updating the source documents (if the new setting above isn’t activated).

15.2.0.8

New functionality

A new method in the Qpick interface: PrintConsignment. Changes and bug fixes:
Default parameter values were not assigned correctly if the rules had dependencies on fields on the consignment (e.g. shipping agent)
Consignment Status is now returned to Qpick.
Calculating freight cost after the source document lines for a previous freight cost has been posted as delivered created a second freight cost line on the source document.

15.2.0.7

New functionality

Number of delayed consignments are shown in a tile on the role centers

Changes and bug fixes:

Ship-to Phone No., Ship-to Mobile phone and Ship-to E-mail was only fetched from sales order and inventory pick if Address Type was “Delivery”. This has been changed so these fields are fetched for all address types where “Source Address Type” is “Shipping”.

15.2.0.6

Changes and bug fixes:

It was not possible to prepare a consignment from Qpick a second time if default confirm action was “Release”.

15.2.0.5

Changes and bug fixes:

Packages was not returned in the Qpick ws-interface for consolidated consignments.

15.2.0.4

New functionality:

A new setting on Shipping Agent Service “Use Return Label” that is used as default value for the corresponding field on Consignment (please note that not all carrier products in Logtrade supports return label).

Changes and bug fixes:

When selecting “To Split Point Code” the default customs invoice information was not initiated.
Split Point Rules was not searchable with “Tell-me”.
When address data is fetched from location the name was fetched from Ship-to name in the Company Information. This has been changed so that the name is fetched from the location.
It was not possible to use the “Copy Consignment” function.
The “Copy Consignment” function can now also copy items.
If “From Split-point Code” has a value, the field “Confirm Status” will no longer be defaulted to “Release”. If the setup for “Confirm Status” suggests “Release” then “Confirm Status” will automatically be changed to “Prepare”.
New columns in the table for Cost Calculation Rules: “Shipping Agent No.”, “Shipping Agent Service Code”, “Shipment Method Code”, “From Delivery Post Code” and “To Delivery Post Code”.
Selecting split consignments multiple times created multiple sets of items from the linked split consignments.
Deleting a linked source document from a consignment did not delete the consignment items created from the linked source document.
Warehouse Ledger Entries was created with the wrong sign when items for costs were inserted on a pick line if bin was mandatory on the location.
A new event has been added "LTC ConsHeadCustInvNode".OnAfterCalcCustomsInvoiceLineAmount that allows manipulation of the data that is used for customs invoice lines.
Truncation of text strings longer than 35 characters did not work as expected.
Fieldname for truncated fields was not calculated in the list of truncated values.
Manually added packages in the list of packages opened from the Consignment Package Line did not update the Consignment Package Line.
A Logtrade user mapped to the current user are now used for all requests to Logtrade.

15.2.0.3

Changes and bug fixes:

Calculations on if a consignment is domestic and/or subject for customs fees now use “Ship-to Country/Region Code” in Company Information instead of “Country Region Code” as a replacement for blank country/region code on consignment addresses.
Custom addresses can now be designated for usage as pickup, delivery etc. to avoid using wrong addresses and to support fetching custom pickup addresses in the Qpick API.
Costs are no longer inserted on a sales order if the sales order has been fully prepayment invoiced.
Costs inserted on a sales order no longer inherits the prepayment % from the sales header. It will always insert as 0% prepayment to allow smooth invoicing of the remaining part of a prepayment invoiced sales order.
Package type relation for PALL/PALLET was wrong for blank carrier and carrier product.
Several enhancements in the Qpick API.
Source document was not updated with freight charge amount if there were no freight cost on the consignment. After this change it is possible to enter freight charge amount without doing a freight cost calculation first.
Freight Cost (LCY) has been enabled for manual editing on the consignment.
The action for calculation of freight cost is now always activated and gives instead a descriptive error message if the prerequisites for price query is not met.
Customs Invoice was sent to Logtrade even if there were no items in the consignment.

15.2.0.2

Changes and bug fixes:

It was not possible to create a warehouse pick from an assembly order.
The QPick API did not require Integrated Printing.
The QPick API could not replace automatically created consignment package lines.
The QPick API returned service name as service description.
Several actions are now “Promoted Only”.

15.2.0.1

Changes and bug fixes:

It was not possible to Ship & Invoice a Sales Order.
Reason Code and Reason Text has been added to Consignment Tracking Entry.
It was not possible to use dangerous goods for generic forwarders.

15.2.0.0

New features:

A SOAP interface for creating consignments from the QPick application for handheld devices.
Timetables defined in BC for calculating “Timetable Delivery Date/Time”.
Possibility to define on shipping agent service if weight and/or volume shall be calculated on consignment package lines.

Changes and bug fixes:

It was not possible to fetch items from source document to a package.
Posting delivery of a sales order now clears the package tracking number on the order.
It was not possible to create a consignment from a list of consignment filtered for a specific source document.
Changing Ship-to Address Code on a consignment did not trigger a recalculation of addresses.
Changing posting date on an inventory pick had no effect when posting.
Rule based cost was not calculated.
Lookup of consignment from posted sales shipment now use Tracking No. as filter so that consignments originally created from a sales order can be found from the shipment.
Service Parameter values based on Shipment Value always used the LCY value of the items.

15.1.0.0

New features:

A REST endpoint for pushing tracking status updates from Logtrade directly into Logtrade Connect.
A report for delivery costs based on price quote data from Logtrade.
A report for analyzing delivery performance based on tracking data from carriers.
Get pickup and delivery dates from carriers.
Batch update tracking data from the Released Consignment Journal.
The functionality for creating consignments from Warehouse Pick has been improved significantly.
Generic Services for SMS advice, e-mail advice etc makes services easier to setup.
Automation rules for creating/sending/printing consignments automatically on release or posting of source document, posting of inventory pick and registering warehouse pick.

Changes and bug fixes:

It was not possible to create a consignment from a filtered list of consignment (e.g. filtered on a specific customer) if truncation was necessary.
Future shipment dates did not respect non-working days in the calendar.
Contact Person from Company Information was not used on Consignment Address
The record in Assisted Setup for Logtrade Connect did not have a dedicated Setup Group.
The communication with Logtrade was always using Swedish locale.
Fact Boxes, links and notes has been redesigned on consignment and package.
The Package List did not show up in “Tell me”.
The navigation buttons in the page for calculating freight cost from sales order was missing.
Running in a sandbox will now always use test mode regardless of the setting in Delivery Setup.
Several issues with printing have been resolved.
Role Centers has been redesigned.
“Manage Multiple Consignments” has been renamed to “Consignment Journal”.
It was not possible to open customs invoice settings from the countries/regions list.
The setting for “Whse. Shipment Warehouse Calculation” is now only used when creating consignment directly from a warehouse shipment. When creating from inventory- or warehouse pick the Qty. to handle is now used.
It was not possible to use carrier customer numbers longer than 8 characters.
Allowable services for carriers and products were not fetched by the assisted configuration guide.
The duplicate consignment check now also looks for released consignments.
The Delivery Setup now has a field for Default Language Code that is used for service parameter values based on language code when the customer, vendor etc. does not have a language code.
It was not possible to print a consignment with a customs invoice if the BC client did not use English as current language.
Note of goods was not copied from a sales order.
It is now possible to click on names in the consignment fact box to open the corresponding address card.
The check for duplicate consignments now ignores released consignments.
Terms of delivery location can now also be based on Pickup City and Delivery City.
When creating consignment from a source document the Delivery Terms Location was not populated.
Specifying a shipment template code on a sales order will now clear shipping agent and shipping agent service code on the order since these cannot coexist on a consignment.
Changing a delivery address did not update the consignment.
Sales order is no longer updated with freight cost or other costs when consignment is created based on sales shipment since this was a bit arbitrary depending on if the source document still existed or not.
Error messages when confirming consignments with Logtrade was not always displayed correctly.
“Your Reference” on a sales document are now used as reference for the recipient address on a sales order and the sender on a sales return order
“Your Reference” was not set on consignments for purchase return orders.
Error messages when communicating with Logtrade when sending a consignment or asking for a price quote are now stored in a table and accessible from the consignment cues.
Declared value and Declared Currency Code are no longer used if Customs Invoice No. has a value.
Changed rounding principals for quantities, weights and volumes on customs invoice and delivery note.
The actions for opening a consignment on the Logtrade Web has been removed.
Contact person on address of type Invoicing was fetched from sell-to/buy-from contact on the source document.
The Address type “Customs Fees Payer” was missing on released consignment address and in custom field mappings.

15.0.0.0

Support for BC15
Setup tables can now be accessed from the Manual Setup page
Changes described in version 14.0.0.0 for BC14

Business Central 14

14.3.0.10

Changes and bug fixes:

This version contains the same changes/fixes as 15.3.0.9.

14.3.0.9

Changes and bug fixes:

This version contains the same changes/fixes as 15.3.0.9.

14.3.0.8

Changes and bug fixes:

This version contains the same changes/fixes as 15.3.0.8.

14.3.0.7

Changes and bug fixes:

This version contains the same changes/fixes as 15.3.0.7.

14.3.0.6

This version contains the same changes/fixes as 15.3.0.6.

14.3.0.5

This version contains the same changes/fixes as 15.3.0.5.

14.3.0.4

This version contains the same changes/fixes as 15.3.0.4.

14.3.0.3

This version contains the same changes/fixes as 15.3.0.3.

14.3.0.2

This version contains the same changes/fixes as 15.3.0.2.

14.3.0.1

This version contains the same changes/fixes as 15.3.0.2.

14.3.0.0

This version contains the same changes/fixes as 15.3.0.0.

14.2.0.8

This version contains the same changes/fixes as 15.2.0.8.

14.2.0.7

This version contains the same changes/fixes as 15.2.0.7.

14.2.0.6

This version contains the same changes/fixes as 15.2.0.6.

14.2.0.5

This version contains the same changes/fixes as 15.2.0.5.

14.2.0.4

This version contains the same changes/fixes as 15.2.0.4.

14.2.0.3

This version contains the same changes/fixes as 15.2.0.3.

14.2.0.2

This version contains the same changes/fixes as 15.2.0.2.

14.2.0.1

This version contains the same changes/fixes as 15.2.0.1.

14.2.0.0

This version contains the same changes/fixes as 15.2.0.0.

14.1.0.0

This version contains the same changes/fixes as 15.1.0.0.

14.0.0.0

It was not possible to lookup address data from the address fact box on the consignment.
It was not possible to link a source document to a consignment if the source document was used on a released consignment.
Linking a source document tried to update the source document with Shipping Agent Code/-Service even if this was turned off in the settings.
Missing captions has been added.
Country of Origin Code was missing when sending customs invoice data to Logtrade.
Print Queue on Consignment was visible/enabled and got assigned even if Integrated Printing was disabled in the setup.
It was not possible to remove Sender Address Code from a Logtrade User.
Carrier customer number was not calculated correctly in all situations.
Default address rules were missing for purchase return orders.
Freight cost are now inserted on sales and service document even if it’s 100% discount
Freight cost inserted on sales or service document now use the carrier freight charge as unit cost.
Previously charged freight and costs are no longer included when using the Copy Document function.
Freight and costs are no longer inserted on purchase order/return order and sales return order
Shortcut keys in consignment has been redefined.

2.0.2.0

It was not possible to post a sales shipment because of a permission error.

2.0.1.0

It was not possible to use items with description longer than 35 characters.

2.0.0.0

This version introduces many new features and should be seen a different product compared to 1.0 (even though app-id is the same and data from 1.0 is upgraded). In this version the Consignment is used as the main document in the app and has support for many different kinds of source documents and source types (customer, vendor etc.).

Business Central 13

1.0.1.0

Consignment No. is now cleared on the sales order after delivery or when the consignment is released. This makes consignment 2..n for partial deliveries possible.
It is now possible to change shipping agent/-service on the order to create more than one consignment for the same sales order
The column “Logtrade Status” has been removed from the sales order list since it’s possible to create more than one consignment for an order.
Customs Value and Customs Currency Code is now calculated for international consignments.
Gate Code can now be entered on the sales order.
The customs VAT-number (from the customer) is now sent to Logtrade.
The Logtrade credentials entered when running the setup wizard are now used as a default user that can be used for all communication except creating consignments which require a personal Logtrade user account.
There is now a list of consignments.

1.0.0.2

Address data from Company Information are now fetched from the delivery tab.
Mixing domestic country code with blank on sender/recipient is no longer considered as export
Both sender and recipient’s customer numbers are now stored on the Sales Order and sent to Logtrade. This is mandatory for international consignments.
Sending a consignment to Logtrade with confirm status = Prepare and receiving as Released cased the consignment number not to be saved on the Sales Order.
Payer and payer customer numbers are no longer shown on the inventory pick. This data is considered as part of the agreement with the customer and shall only be changed on the Sales Order.
If the setup is to use the sales orders shipment date for creating the consignment and the sales order has a blank shipment date the current date (Today) is used.
The location name is no longer used as name on labels and documents. The name is now always based on the Ship-to name in the Company Information.

1.0.0.1

Initial version published on AppSource

Table of Contents

Logtrade Connect

Business Central 23.3 and later

24.3

24.2.330.0 (2025-01-08)

24.1.328.0 (2024-12-17)

24.0.323.0 (2024-12-16)

24.0.322.0 (2024-12-13)

23.36.317.0 (2024-12-05)

23.35.312.0 (2024-12-02)

23.34.310.0 (2024-11-26)

23.33.307.0 (2024-11-22)

23.32.304.0 (2024-11-20)

23.31.302.0 (2024-11-19)

23.30.297.0 (2024-10-18)

23.29.295.0 (2024-10-14)

23.28.292.0 (2024-10-09)

23.27.289.0 (2024-10-03)

23.26.286.0 (2024-09-20)

23.25.284.0 (2024-09-09)

23.24.282.0 (2024-09-04)

23.23.280.0 (2024-08-26)

23.22.278.0 (2024-08-21)

23.21.276.0 (2024-06-28)

23.20.274.0 (2024-06-25)

23.19.272.0 (2024-06-19)

23.18.270.0 (2024-06-19)

23.17.267.0 (2024-06-17)

23.16.265.0 (2024-06-10)

23.15.263.0 (2024-05-29)

23.14.260.0 (2024-05-21)

23.13.258.0 (2024-05-17)

23.12.251.0 (2024-04-25)

23.11.249.0 (2024-04-17)

23.10.245.0 (2024-04-12)

23.9.243.0 (2024-04-12)

23.8.241.0 (2024-04-08)

23.7.239.0 (2024-04-03)

23.6.237.0 (2024-04-03)

23.5.235.0 (2024-03-27)

24.4.233.0 (2024-03-25)

23.3.231.0 (2024-03-19)

23.2.228.0 (2024-03-13)

23.1.226.0 (2024-03-07)

23.0.224.0 (2024-03-01)

Business Central 20 to 23.2

20.42.0.0 (2024-09-11)

20.41.0.0 (2024-04-03)

20.40.221.0 (2024-02-21)

20.39.218.0 (2024-02-12)

20.38.216.0 (2024-02-09)

20.37.214.0 (2024-01-24)

20.36.212.0 (2024-01-10)

20.35.210.0 (2024-01-09)

20.34.204.0 (2023-12-28)

20.33.202.0 (2023-12-21)

20.32.198.0 (2023-12-13)

20.31.194.0 (2023-12-11)

20.30.192.0 (2023-12-11)

Note

20.29.190.0 (2023-11-23)

20.28.187.0 (2023-11-17)

20.27.184.0 (2023-11-13)

20.26.183.0 (2023-11-09)

20.25.181.0 (2023-10-26)

20.24.179.0 (2023-10-23)

20.23.176.0 (2023-09-28)

20.22.174.0 (2023-09-25)

20.21.166.0 (2023-09-06)

20.20.162.0 (2023-09-06)

20.19.158.0 (2023-06-14)

20.18.156.0 (2023-05-31)

20.17.154.0 (2023-04-24)

20.16.150.0 (2023-04-18)

20.15.147.0 (2023-03-24)

20.14.139.0 (2023-03-24)

20.13.88.0 (2023-03-14)

20.12.70.0 (2023-02-22)

20.11.67.0 (2023-01-17)

20.10.57.0 (2023-01-16)