...
Version | Release Date |
|---|---|
22.10.2398.0 | 16-11-2023 |
The following issues have been resolved: |
|---|
nShift Ship changed the url for the api communication of their sandboxes. |
A type cast error could occur when empty values are set on the Transsmart portal for the package dimensions. |
When using Sendcloud in combination with the Mobile WMS integration the default package was not automatically assigned in all circumstances. |
When using Sendcloud in combination with the Mobile WMS integration the default services were not set on created packages. |
When changing the weight on a Mobile Device that weight was set as net weight, while gross weight is intended. |
nShift Transsmart now enforces language codes in iso format, which means that they must be lowercase. |
Updating the posted documents with the actual shipping agent and the tracking information has been limited and changed, because of locking issues. |
The following improvements have been implemented: |
|---|
It is now possible to indicate that packages that are created on sales documents (quotes or orders) should not be copied to transport orders. |
Several improvements have been implemented in the synchronization with nShift Transsmart: |
There are also improvements for retrieving documents and labels from nShift Transsmart: |
Additional events have been added to the procedure that creates transport orders, making it easier to add customizations to the transport orders. |
New product videos have been included, you can view them from the ShipIT Manager Role Center. |
Version | Release Date |
|---|---|
22.9.2296.0 | 12-10-2023 |
The following issues have been resolved: |
|---|
The following error message could occur when creating a transport order: |
When syncing basic data from Delivery Hub an error message could occur that the filtered text exceeded the maximum allowed length of the field (250 characters). |
Version | Release Date |
|---|---|
22.9.2269.0 | 05-09-2023 |
The following issues have been resolved: |
|---|
A duplicate provider setup record was created after renaming Delivery Hub to nShift Ship. |
The license keys for the Easypost app wasn’t working correctly. |
| Info |
|---|
For a correct determination of the available services, a resync of the Basic Data with nShift Ship is required after updating to this version. The basic data can be synchronized from the nShift Ship Provider Setup page. |
The following improvements have been implemented: |
|---|
Support for Deny Countries in the nShift Ship basic data synchronization and filtering on available services based on ship-from and ship-to country. |
Carrier Select is now available for nShift Ship. |
Version | Release Date |
|---|---|
21.9.2042.1 | 14-07-2023 |
The following improvements have been implemented: |
|---|
This is a minor release, with a small change required for internal purposes. |
Version | Release Date |
|---|---|
21.9.2042.0 | 13-07-2023 |
The following improvements have been implemented: |
|---|
The standard BC permission set to Read Basic data (D365BASIC) has been extended with the permissions to read the Setup and the Provider setup. |
DeliveryHub has been renamed to nShift Ship and Transsmart to nShift Transsmart, reflecting the new names of these solutions by nShift. |
The following issues have been resolved: |
|---|
Manually creating a transport order from the card page failed when enabling a default package. |
The batch Job to delete completed and outdated transport orders failed for transport orders with the status “DONE”. |
An issue in the Package Details Factbox on the Transport Order Card occasionally resulted in an error that the record in the Transport Order Package table already existed. |
The prices on the transport orders, like spotprice and costprice, were not cleared when reset or recalling a transport order. |
Version | Release Date |
|---|---|
21.9.1975.0 | 14-06-2023 |
The following issues have been resolved: |
|---|
When unexpected errors occur during the master data synchronization with Transsmart the returned error message was not returned. |
Calculation of Qty. Sent on warehouse shipment lines mixed up returns and orders when the No. Series overlapped. |
The calculated weight of a package was doubled in the communication to Transsmart.| |
Precautions have been taken to prevent an error message on the status of the document when a (temporary) Sales Header is inserted in a released state. |
...
Version |
|---|
...
Release Date |
|---|
...
...
21.9.1937.0 |
...
30-05-2023 |
...
...
The following |
|---|
...
issues have been |
|---|
...
resolved: |
|---|
...
...
It is now possible to configure default service levels (other), for the nShift - |
...
Ship provider. |
...
...
Token refresh failed, when working with the Beta feature "Create and Book Transport Order(s)". |
...
...
Retrieving the MD5Hash failed in the BC14 version |
...
Precautions have been taken to prevent an error message on the status of the document when a (temporary) Sales Header is inserted in a released state. |
Version | Release Date |
|---|---|
21.8.1855.0 |
...
11-04-2023 |
...
...
The following improvements have been implemented: |
|---|
...
...
EasyPost has been added as a provider for ShipIT |
...
...
The following |
|---|
...
improvements have been resolved: |
|---|
...
...
An error could occur during the to the latest version on a non-unique IDYS Provider Carrier."Entry No". |
...
...
The transport worksheet didn't propose sales orders. |
...
Q1 2023|.
Version |
|---|
...
Release Date |
|---|
...
...
21.8.1790.0 |
...
28-03-2023 |
...
The following improvements have been implemented: |
|---|
It is now possible to indicate on a Shipment Method that transport orders are not required. |
The following improvements have been resolved: |
|---|
...
...
Non-inventory were not accepted on Source document when trying to set ShipIT quantity to Send. |
...
...
Page view issue when creating a new sales order directly from the Customer Card. |
...
...
When inserting a Sales Header a sub table is populated in ShipIT, this shouldn't occur when the Sales Header is a temporary record. |
...
...
The total weight on the Transport Order wasn't directly updated when the quantities were changed.| |
...
It was not possible to create a Transport Order without a default package when Linking Package Content was activated. |
...
...
Ship: The labels were downloaded in the wrong format (as a PDF instead of a Zip). |
...
|_. The following improvements have been implemented: |
| It is now possible to indicate on a Shipment Method that transport orders are not required.|
...
Version | Release Date |
|---|---|
21.8.1640.0 |
...
01-03-2023 |
...
...
The following |
|---|
...
improvements have been resolved: |
|---|
...
...
The ShipIT application is now available with Sendcloud embedded as a provider. |
...
...
Carrier selection is available on the sales quote and sales return orders. |
...
...
Adding freightcost with Carrier Selection is integrated to work with default business central service charge. |
...
...
Default insert of the transsmart Costcenter is now active on transfer orders. |
...
...
Debugging is allowed from BC19 and higher versions. |
...
...
Version |
|---|
...
Release Date |
|---|
...
...
21.8.1487.0 |
...
29-01-2023 |
...
...
The following |
|---|
...
improvements have been resolved: |
|---|
...
...
The action to add additional packages to the transport order and sales order was hidden for several installations. |
...
...
The creation of transport orders for sales return orders failed when Transport Orders were based on Posted Documents or when using WMS locations. |
...
...
Version |
|---|
...
Release Date |
|---|
...
...
21.8.1460.0 |
...
25-01-2023 |
...
...
The following improvements have been |
|---|
...
resolved: |
|---|
...
...
Added an action to add additional packages to the transport order and sales order. |
...
...
Version |
|---|
...
Release Date |
|---|
...
...
21.8.1443.0 |
...
20-01-2023 |
...
...
The following improvements have been implemented: |
|---|
...
...
When adding Freight charges to sales orders is enabled, the Service Account No. from the Customer Posting Group is now used on the sales line that is created. |
...
This allows users to setup different G/L Accounts for different Customer Posting Groups. |
...
It also solves the issue that the Freight G/L Account No. on the Sales & Receivable Setup is not visible by default. |
...
...
The Shipment Method Code is no longer a required field for the creation of Transport Orders, except for |
...
Ship. |
...
...
The calculation of the combinability hash key, which was used to determine if transport orders can be combined, is no longer using external API calls. |
...
...
There is now a conversion factor for weight and volume for every provider. If the weight or volume on the item card or sales orders is registered in a different unit of measure, |
...
then the default user of measure of the provider (Transsmart/DeliveryHub/Sendcloud) the weight and volumes can be automatically converted using this conversion factor. |
...
Examples are lbs to kg (for Transsmart). Conversion factors can be set on the Provider specific Setup page. |
...
...
The following |
|---|
...
improvements have been resolved: |
|---|
...
...
The calculated package weight doubled, when the weight on a delivery note line was changed manually on a transport order. |
...
...
When calculating the total weight of the transport order the actual weight was ignored. |
...
...
A couple of obsolete pages were still visible from the context search menu. |
...
...
From BC18 and lower versions it was not possible to select the Package Code on the Sales - and Transport Order |
...
...
Creating delivery note lines linked to packages through |
...
|. Version |. Release Date |
| 21.8.1410.0 | 15-12-2022 |
p(banner tip). Remark for On-Prem installations:
With the release of ShipIT 21.8.1300.0 a new install app has been introduced for BC14 and BC15.
This install app, Idyn App Management, needs to be added to the licenses.
When upgrading to this new version for customers on BC14 or BC15, please ensure that you refresh your development – and customer licenses.
|_. The following improvements have been implemented: |
| The solution is prepared for the Deliveryhub integration from nShift. If you're interested in implementing with Deliveryhub please contact sales@idyn.nl|
|_. The following issues have been resolved: |
| The weight for goods in Unit of Measure was not set correctly on Delivery Note Lines.|
| Several improvements in Carrier Select functionality.|
p(banner tip). When you are working with quantity in decimals or different Sales Unit of measures on your sales orders the outstanding shipments can have a faulty Qty to send after upgrading. This can result in wrong quantity values in your transportorder. Therefore a separate correction batch is available. Install this correction batch in extension management and update your Qty (Base) fields if needed. You can start this batch from the ShipIT setup. Click Actions and Gty. (Base) Correction. After correction uninstall the batch .
!{IMAGE-LINK+corection-batch}!
p(banner important). Important info. for non SUPER users you have to include the permissionset IDYSR ShipIT QtyBase to the user.
p(banner important). You can run this batch only 1 time for each separate company. If needed you can debug the code.
|. Version |. Release Date |
| 21.7.1226.0 | 22-11-2022 |
|_. The following issues have been resolved: |
| The weight for goods in Unit of Measure was not set correctly on Delivery Note Lines.|
| The Pick-up and delivery time were not respecting time zone differences. This has been adjusted.|
| Several improvements in Carrier Select functionality on the Sales Orders.|
| ShipIT Qty. to Send was not cleared when changing the sales lines to a location with WMS handling.|
| The default package was added again on the Transport Order when it was removed on the Sales Order.|
| The default package was added again on the Transport Order when it was removed on the Sales Order.|
| The number of packages doubled on the Transport Order when it was copied from Sales Order Packages.|
| Improvements for enabling the Linking package content functionality: |
| The calculated weight of a package with linked content was incorrect. |
| During the upgrade an error could occur, because the api call to check our license was blocked in this process.|
|. Version |. Release Date |
| 20.7.1079.0 | 18-10-2022 |
|_. 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 Transsmart and is rejected by a few carriers.|
|. Version |. Release Date |
| 20.7.977.0 | 30-09-2022 |
p(banner tip). Remark for Saas / Cloud environments:
With the release of ShipIT 20.7.977.0 a new install app has been introduced.
This install app, Idyn App Management, will be automatically installed when you do a fresh install of this version of ShipIT.
However, when updating ShipIT from a version prior to ShipIT 20.7.977.0 then the Idyn App Management app is not automatically rolled out.
This results in the following error message:
!(zoom){IMAGE-LINK+shipitappmanagementinstallerror}!
To resolve this:
Uninstall ShipIT via Extension Management.
Don't set the Delete Extension Data flagInstall the latest version of ShipIT via Extension Marketplace.
p(banner tip). Remark for On-Prem installations:
With the release of ShipIT 20.7.977.0 a new install app has been introduced.
This install app, Idyn App Management, needs to be added to the licenses.
When upgrading to this new version, please ensure that you refresh your development – and customer licenses.
|_. The following improvements have been implemented: |
|It is now possible to assign the delivery note information (items) to the packages.
Additional costs apply, please contact sales@idyn.nl for more details.
This means that the carrier knows exactly which goods are in a package, which can be a requirement for some carriers for cross-border shipments.|
|We have implemented a different API to retrieve the statuses of transport orders from Transsmart.
This solves the Rate Delimiter errors that might occur when the statuses of Transsmart shipments were requested in bulk via the job queue.|
|_. The following issues have been resolved: |
| The registered username was not accepted on new implementations in the Setup Wizard. This has now been resolved.|
| High volume customers got a rate delimiter error on shipment calls. Several changes have been implemented to prevent these issues.|
| The shipping agent and shipping agent service is no longer mandatory, when using the Carrier Select functionality on a Sales Order.|
|. Version |. Release Date |
| 19.7.704.0 | 18-08-2022 |
|_. 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 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":{TOPIC-LINK+customize-the-calculation-of-qty-to-send-on-source-documents}.|
|. Version |. Release Date |
| 19.7.0.0 | 11-05-2022 |
|_. The following issues have been resolved: |
|The Bing Maps Factbox gave an error, because of license issues.
On the ShipIT Setup Card or - Wizard create and setup a personal Bing Maps key.|
|The City or County was cleared when converting source documents to transport orders.|
|The total amount of the commercial invoice was incorrect.|
|The License Plate No. has been extended to 20 characters. This field is used by the Tasklet integration.|
|. Version |. Release Date |
| 19.6.12230.0 | 10-03-2022 |
...
the |
...
Transport Order |
...
API |
...
|_. The following improvements have been implemented: |
|Additional fields and factboxes have been added to the Transport Order List and - Card.|
|. Version |. Release Date |
| 19.6.12225.0 | 17-02-2022 |
|_. The following issues have been resolved: |
| The Phone number and House number are no longer mandatory fields when creating or posting transport orders. |
| Dutch translation issue on the ShipIT Setup. |
| No validation errors occur when working with negative quantities on sales orders and service orders.
Additional development is required to support the flow where negative quantities are handled as reversed logistics.
This will be developed in a future release. |
|. Version |. Release Date |
| 19.6.12220.0 | 13-01-2022 |
|_. The following issues have been resolved: |
| The currency code on Delivery Note Lines was not correctly communicated to 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. |
|. Version |. Release Date |
| 19.6.12000.0 | 20-12-2021 |
|_. The following issues have been resolved: |
| The Transport Order Details Factbox on source documents (e.g. a sales order) was showing total values for all the existing transport orders,
when a transport order didn't exist for the source document . |
| When using Batch Posting or when posting warehouse shipments a confirm to view the created or updated transport order was given for every order that was booked.
There is now one notification for all the transport orders that are created or updated when posting a batch. |
| Combining transport orders didn't always work as expected when working with warehouse shipments.
Especially when the Shipping Agent or - Service is changed on the warehouse shipment.
The cause was that Business Central updates the Shipping Agent and - Service on the source documents without validation.
As a result, the Shipping Time on the source document does no longer reflect the actual shipping times for the selected carrier. |
|_. The following improvements have been implemented: |
| It is now possible to Create, Book and Print a transport order when shipping a source document (e.g., a sales order).
This has been implemented as a Beta feature, because the basic data needs to be accurate on the source documents for this process to work efficiently.
We therefore believe that this feature is not recommended for all customers.
Beta features can be enabled on the ShipIT Setup.
When enabling the Beta features additional options will be available in the After Posting options on the same page.
Beta features are pre-released features that in it's current shape have limitations in the supported usage scenarios or they are new features that have not been fully tested.
Because of the nature of Beta features, we give limited support on them. Support tickets may be raised with suggestions and general feedback,
but issues will only be solved in newer versions of the product and not on a per customer basis. |
|. Version |. Release Date |
| 19.6.11120.0 | 24-11-2021 |
...
was |
...
|_. The following improvements have been implemented: |
| The Tracking Information from Transsmart, like the tracking no. and the tracking URL are now updated on all source documents.
Previously the tracking information were only updated on the sales order and the sales shipment. |
| The Shipment Method Code is now also copied from the source documents to the warehouse shipment,
when all source document lines use the same Shipment Method. |
| It is now possible to setup a different behavior with regards to the creation of transport orders after posting sales return orders compared to sales orders.
Previously, there was only one setting (the "After Posting Sales Orders" field in the ShipIT Setup) which was also applied when handling sales return orders.|
| On the Item Unit of Measure a package type can be mapped. When items are sold a unit of measure with a package type setup,
then the required number of packages will be automatically added to transport order. |
| It's now possible to select multiple transport orders in the transport order list and perform actions like booking, printing, synchronizing, etc... for multiple transport orders. |
| The notification or warning that is given when a transport order has been created after posting a source document can now be suppressed.
This is a setting in the ShipIT Setup (field Suppress Transport Order Created Notification) |
|. Version |. Release Date |
| 19.6.11000.0 | 08-11-2021 |
|_. The following issues have been resolved: |
| The shipment values on the transport order were not correctly calculated when transport orders were manually created from a posted document.
Or when the source document was deleted during the posting routine.
E.g., when the transport order was automatically created after completely shipping and invoicing a sales order.
The prices were either blank or they were not based on amounts including VAT. |
| The preferred delivery date was not correctly determined when creating a transport order from a sales return order. |
| Due to a translation issue in the French localization, the communication with Transsmart was not working. |
| The Delivery Notes did not contain the right values when working with partial deliveries. |
|_. The following improvements have been implemented: |
| The Application Area “Location” is used for everything related to Transfer Orders. |
| The source document no. and the customer number are now included in the communication with Transsmart. |
|. Version |. Release Date |
| 19.6.10925.0 | 11-10-2021 |
|_. The following issues have been resolved: |
| Splitting the address into a street and a house number was inefficient when numbers were used in the street name or when the house number had an addition (E.g., 1st Cross street 20 a) |
| Qty. to Send was not reset after creating a transport order from a posted document |
| When using multiple warehouse shipments for a single source line (e.g., a sales order line), then the process can give an error that the ShipIT Quantity to Send field exceeds the quantity.
This can happen during the creation of the shipment or when registering the pick (or changing Qty. to Ship manually).
The cause of this is that when the second warehouse shipment line is created the remaining quantity of the source line is set as the (total) quantity on the warehouse shipment line.
So, ShipIT Quantity to Send should not be compared against the quantities on the warehouse shipment line.
Instead, the quantities of the source document should be used. |
...
causing |
...
|. Version |. Release Date |
| 18.5.10911.0 | 19-09-2021 |
...
issues |
...
|_. The following improvements have been implemented: |
| The Sales Document is no longer reopened when a transport order is created from a sales shipment. |
| Delivery Notes are now created for all source documents. |
...
. |
...