Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type null in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 36

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type null in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 36

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type null in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 36

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type null in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 36

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type null in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 35

Warning: Trying to access array offset on value of type bool in /www/connectlogtradese_760/public/wp-content/themes/logtrade-theme/single-connector-updates.php on line 36

Version 17.4.0.0 (released 2021-06-14)

This version has it's focus on high volume scenarios where incoming sales orders are validated against LogTrade on release of the order and only successful validations releases the sales order. This will keep the errors (post codes etc) away from the inventory workers and streamline the process. We have also introduced a flexible concept of identifiers which can be used to further identify addresses, packages and consignments. Currently a common use is VOEC- and EORI-numbers.

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”.

More news about Microsoft Dynamics 365
Business Central

Version 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”.

Version 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.

Version 19.2.0.4

Changes and bug fixes:

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

Version 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.

Version 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.