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 15.2.0.5 (released 2020-05-15)

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.

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.