Version 10 (released 2013-11-25)
This version supports 2013 R2 and are in many terms an RTC-release with a brand-new Role Center for LTC, fact boxes etc. Other big changes are the support for Warehouse Shipments and creating Consignments for already posted documents.
New functionality:
- The XML file logging on the file system has been replaced with table-based logging and XML files stored as blobs.
- There is now a Role Center for LogTrade Connect. Several pages have also been changed to include fact boxes with Consignment statistics. For the classic client statistics forms (F9) has been added. Some fields have been moved from the Consignment to the Consignment fact box.
- LogTrade Connect now supports Warehouse Shipments. One or more Consignments can be linked to a Warehouse Shipment and there is also a function to automatically created all consignments necessary for a Warehouse Shipment. (Advanced Management)
- To support Warehouse Shipments where several Source Documents for the same recipient can be treated at once it is now possible to link source documents to a Consignment. The consignment will have one “main document” and other source documents of the same type for the same recipient can be linked. Linking can be done manually, from a Warehouse Shipment or by using a function on the Consignment to find Source Documents for the same recipient to add as Linked Documents.
- Four new Source Document Types has been added: – Sales Shipment – Return Shipment – Transfer Shipment – Service Shipment
- There is now a function (CheckConsignment) in codeunit 12057533 that can be called from e.g. codeunit 80 to verify that a Consignment exists and is sent as Prepared. Otherwise the user is prompted to create or open the Consignment.
- The functions for Post Code verification now supports setting up Post Code Check Shipment Templates per Country and Shipping Agent instead of only per country as earlier. This means that you can test postcodes on customers, orders etc. with e.g. SCHENKER with one template and all others with a default template for that country.
- Country/Region Code is now a part of the primary key in the Payer Customer No. table meaning that it is now possible to have one customer number for e.g. Sweden and a different customer number for other countries on the same forwarder and product.
- The payment terms description copied to a customs invoice are now always in English if an English translation exists for the payment term.
- Many default settings for customs invoice has been added together with the possibility to import a picture for signature.
- There is now a document in NAV for Customs Invoice, and it is possible to choose in the setup if Customs Invoice should be printed by NAV or not. If printed by NAV it will be printed automatically if Print Method = “LogTrade Controlled” and the status after sending the Consignment is “Prepared” or “Released”. This opportunity makes it easy to implement custom specific layout requirements for Customs Invoice.
- It is now possible to specify a Shipment Template Code on a Forwarder Product. If specified, the Shipment Template Code will be automatically added to the Consignment when validating the Shipping Agent Service Code that is linked to the product.
- It is now possible to call a LogTrade webservice from the Consignment to get the pickup date/time and delivery date/time for the Consignment. The answer from LogTrade is shown in a message box.
- The error message from LogTrade about missing Shipping method code/Leveransvillkor is now translated to “Terms of Delivery Code”/Transportvillkor.
- The Worksheet for Released Consignments referenced non released Consignments in all page links and the batch print function. This has been corrected.
- Sender reference for sales order was not populated with External Doc. No. from Sales Order or Vendors Order No. for Purchase orders. This has been corrected.
- Calculations of weight and volume are now based on outstanding quantity instead of Qty. to Ship. The reason for this is the support for Warehouse Shipment.
- All code for truncation in table 12057521 has been moved to a separate codeunit to make the code in the table more readable
- The definition of the service parameter calculated value “Outstanding Qty. to Ship Value” has been changed to “Qty. to Ship Value/Qty. shipped Value” (based on “Line Amount” instead of “Outstanding Amount”) to support using posted documents as source documents.
- Terms of Payment on Customs Invoice are now populated automatically based on the Payment Term of the Source Document when Source Document Type = Sales Order
- It was not possible to create manual text lines in the Customs Invoice
- It is now optional if Customs Invoice lines shall be aggregated on source document descriptions. If not, aggregation will be on Tariff Number.
- It is no longer possible to enter package number manually unless the product is setup for manual package numbers
- Sender Address Code was not always cleared as it should when changing location code etc. This has been corrected.
- If “From Split Point Code” was cleared the sender and pickup information was not restored correctly. This has been corrected.
- If the user is linked to an employee in the user setup the “Sender Mobile Phone No.” is now fetched from the employee. “Phone No. 2” from Location and Company Information is no longer used as “Mobile Phone No.”.
- The Setup Wizard has been redesigned slightly to make setup more intuitive. The user is now prompted with a LogTrade logon dialog which after loon will load the forwarders and products and then open the wizard.
- You must make sure that the fields “Save XML Request” and “XML File Path” are empty before importing the objects since these two fields are removed in this version.
- If you are upgrading and are using RTC you must run codeunit 12057547 manually to initialize the charts used in the LTC role center.
- If you are upgrading and want to use the Time Table function you must setup the codeunit ID (12057549) for Time Table queries in the Advanced Setup.
