...
The following issues have been resolved: |
---|
Retrieving the status of transport order bookings gave errors, when the language was not set to English. |
The amount on the transport order line was multiplied with the base quantities (quantities in unit of measure) twice. |
The description of the packages on a transport order were copied from the package type, this is not the expected input in nShift Transsmart and is rejected by a few carriers. |
...
The following improvements have been implemented: |
---|
It is now possible to assign the delivery note information (items) to the packages. |
We have implemented a different API to retrieve the statuses of transport orders from nShift Transsmart. |
...
The following improvements have been implemented: |
---|
Support for Variant Codes has been added to the Transport Orders. The Variant Code is visible on the Delivery Note Lines and in the communication with nShift Transsmart the Item No. and Variant Code are combined. |
It is now possible to customize the calculation of qty. to send on source documents or to disable the error for over-shipping. Click here for more info. |
...
The following issues have been resolved: |
---|
For some source documents the lines with zero quantities were forwarded to the Transport Order. |
Creating a Sales Quote for a Contact gave an error about a missing customer no. |
currency in the Delivery Note Info Line was not populated in the transsmart nShift Transsmart Shipment API. |
The following improvements have been implemented: |
---|
Additional fields and factboxes have been added to the Transport Order List and – Card. |
...
The following issues have been resolved: |
---|
The currency code on Delivery Note Lines was not correctly communicated to nShift Transsmart. |
The default cost center from the ShipIT Setup was not used for transport orders created from sales orders or purchase return orders. |
In some situations the parameters for the job queue entries that ShipIT uses were obmitted. |
The calculation of the transport order value was incorrect. |
...