Notice: 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

Notice: 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

Notice: 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 5 (released 2012-11-30)

This version introduces the Customs Invoice, a new setting for default Shipment Date on consignment and a new separate field for Sender Reference. Besides that, there are bug fixes and GUI enhancements. New functionality:
  • Customs Invoice is now supported. It is now possible to create a customs invoice linked to a consignment automatically (if there is a source document) or manually given that the recipients country code is not blank and not an EU country. The Customs Invoice is printed together with the other LogTrade documents.
  • The default shipment date can now be based on the source document.
  • Sender Reference now has its own field on the consignment instead of using Source Document No. This makes it possible to create consignments without using a source document where the Shipping Agent Service requires a sender reference (such as DHL Express). By default, the Source Document No. is used to populate the Sender Reference field.
Bug fixes/changes:
  • If validated shipments were released in the LogTrade Web GUI instead of using the Consignment Worksheet, an error occurred if you after that tried to release the consignments in NAV. This has been changed so no error message is shown. Instead these consignments are left in the worksheet and it is now possible to update status from LogTrade by choosing “Update Status from LogTrade”. This way the consignments will be released also in NAV. If “Update status in Worksheet” is enabled in setup the consignments will also be updated automatically when the worksheet is opened.
  • If the xml-filed used by the import/export function did not exist, the user had to close the import progress dialog manually. This has been corrected.
  • If Settings where to save XML response but no path for XML file was setup the Service Tier tried to save the response in an unpredictable folder often with an access violation error as result.
  • When using “Address Code” without a Source Document the Post Code was not populated. This has been corrected.
  • When using Address Code with Source type “Customer” and no source document the Shipment Method Code was not fetched from the Ship-to Address. This has been corrected.
  • When changing Post Code on a consignment with no source document but with a source address code (shipping/order address) the customer/vendor was updated with the new post code instead of the customer/vendor. This has been corrected
  • When changing Post Code on a consignment with a sales document with a ship-to address <> ” as source document the ship-to address was not updated with the new Post Code. This has been corrected.
  • It was not possible to disable saving of password in xml debug files. This has been corrected.
  • It was not possible to drill down in “No. of services” on Consignment. This has been changed so that drill down is possible, and no. of services updated on return to the Consignment
  • When drilling down from “No. of missing parameters” on a consignment service only the missing parameters where shown. This has been changed so that all parameters for the service are shown.
  • When a service is added which has a parameter of the type “CurrencyCode” the currency code is automatically fetched from the source document (or the source no. if there’s no source document). If the currency code still is blank it is automatically set to the LCY Currency specified in General Ledger Setup (regardless if that currency code exists as a currency). Otherwise it won’t be possible to send the consignment using local currency without setting up the local currency as a currency since that parameter would miss a value.

More news about Microsoft Dynamics NAV

Version 27.30

Bug fixes/changes:

  • Dangerous goods lines were not created for a split consignment when the linked split consignments had dangerous goods.
  • It was not possible to create a customs invoice where the relation between sender and delivery was not customs liable but the relation between pickup and delivery were.

Version 27.29

Version 27.28 (released 2021-08-26)

Version 27.27 (released 2021-06-16)

Version 27.26 (released 2021-03-01)

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