Version 17 (released 2015-02-22)
From this version. NAV5.0 and NAV2009 are no longer fully maintained. NAV2013 is the “base version” and 5.0/2009 only get critical fixes.
** Before importing this fob, you must manually remove page 12060770 (if it’s there) **
When importing this fob in NAV 2015 you will get an error when the schema changes are synchronized since two fields have been removed from table 12057524. If you have no errors from other tables, you can synchronize with force.
New functionality:
- Automated assignment of Shipment Template based on rule-based setup similar to Sender Address Setup etc.
- It is now possible to archive a released Consignment. This will also archive the Consignment in LogTrade
- NAV2015 Tablet GUI. Take a look at page 12060708 “LogTrade Mini Role Center”!
- Creating a consignment from the LogTrade Role Center and the Consignment list now inserts a Consignment and opens it. This is needed for smooth work on a tablet.
- When sending Recipient County to LogTrade the field Province was used instead.
- When Consignment was released in the Web GUI the Tracking No. cold be lost in NAV causing errors when updating the status from the Consignment Worksheet.
- Minor GUI changes on Consignment pages.
- Calculation of Customs Invoice Lines now include consolidated Consignments.
- Sender Address Code has been extended to 25 characters
- Payer Customer No. was not calculated on Consignments for Sales Return Order and Purchase Order
- Consignment deletion from the Consignment List did not send an archive request to LogTrade
- Consignment Notifications now also support the trigger “On Archive” which will send a cancellation message.
- When choosing Sender Address Code on a Consignment the name, address etc. are now fetched from the Sender Address. It’s just for the GUI. The sender Address Code is still sent to LogTrade.
- When printing Customs Invoice in NAV for a Consignment with blank Location Code and a non-blank Sender Address Code the Sender Country Name (fetched from the Company Information) was not printed.
- A complete set of name/address fields has been added for Recipient. The existing name /address fields has been renamed to “Delivery Name”, “Delivery Address” etc. Existing logic still apply for delivery name/address fields. Recipient fields are populated from sell-to/buy-from, ship-to or bill-to/bill-from depending on setup. The default is “Ship-to” to preserve current logic. On Customs Invoice the “Recipient”-fields are used instead of the delivery name/address as today.
- Truncation did not work when several consignments needed truncation at the same time (when creating consignments from whse shipment)
- An error was thrown when creating consignments from whse shipments if any of the source documents had name/address longer than 35 characters.
- It was not possible to create consignments for posted documents.
- Truncation no longer updates orders, customers etc. with truncated values. Instead a Truncation Rule table has been created which is maintained automatically when truncation occurs. This way a string too long to fit in LogTrade will get truncated automatically based on the rule the next time it’s used on a Consignment.
- Since version 16 the lines collected to Customs Invoice was not correct if Source Document Type was “Sales Order” and the Customs Invoice was created before the Consignment was sent to LogTrade for validation.
- If automatic creation of Consignment Line is activated the Consignment line was created with AnyForwarder and AnyProduct
- When sending e-mails from NAV the language is now defaulted to ENU if the source has a Language code not equal to blank or SVE.
- Calculation of quantity, weight and volume from Warehouse Shipment was not correct when any of the lines was missing in inventory
- The Price Quote page was in the Adv. Mgmt. Object No. area.
