Page Comparison

...

You must review and answer the questions below to request the Migration tool from Tasklet

Do you have any customization created for Pack & Ship?

1. No → OK
2. Yes → Have you successfully updated your customization as instructed?
   1. No → You must do it to continue
   2. Yes → OK

Are you using the ShipIt 365 connector by Tasklet?

1. No → OK
2. Yes → You must wait until the new AppSource extension provided by Idyn is ready, expected September 2023

Are you using the LogTrade connector by Tasklet?

1. No → OK 
2. Yes → Have you identified the latest version, compatible with Mobile WMS from Microsft AppSource?
   1. No → You must do it to continue
   2. Yes → OK

Do you have any customization created for ShipIt 365 connector or LogTrade connector?

1. 1. No → OK
   2. Yes → You need to talk with a developer from Tasklet to verify your customization

Do you understand the how-to migration guide?

1. 1. No → Request a meeting with a developer from Tasklet for help
   2. Yes → OK

Please confirm that you will test the migration in a copy of the production environment to verify the migration result.

Technical description of Pack & Ship Migration Tool

Introduction

The purpose of the tool is to move data from the Pack & Ship extension to new tables in Mobile WMS. The tool consists of two main actions: Backup and Restore.

The tool handles standard fields in Pack & Ship but also fields added to Pack & Ship tables from both connectors and custom extensions. This mean you will not need to handle data migration during upgrade of your custom extensions on Pack & Ship even though the fields are moved from a Pack & Ship (MOS) table to a Mobile WMS (MOB) table. It is just required your table extensions on MOS tables are installed during the Backup process and your new MOB table extensions are installed during the Restore process and the have the same field numbers and field types.

Pack & Ship Data Backup

The backup starts by copying the contents from all Pack & Ship tables (prefixed MOS) to Mobile WMS tables (prefixed MOB):

• MOS License Plate → MOB License Plate
• MOS License Plate Content → MOB License Plate Content
• MOS Package Type → MOB Package Type
• MOS Package Setup → MOB Package Setup
• MOS Packing Station → MOB Packing Station
• MOS Shipping Provider → MOB Shipping Provider

Next it will go through all non Pack & Ship fields in the above MOS tables and save the values in an intermediate table. It will only save field values of installed extensions, so it is important all used extensions are still installed when the Data Backup is executed.

It will then extract field values from table extensions in the Logtrade and ShipIT 365 connectors in non Pack & Ship tables.

Finally it will update the GetPackingOrders document type so it points to the new handler codeunit in Mobile WMS.

The contents of this table can be viewed from Mobile Pack & Ship Migration Tool by drilling down in the "No. of Field Values":

Image Added

Pack & Ship Data Restore

The restore loops through the following tables:

• MOB License Plate
• MOB License Plate Content
• MOB Package Type
• MOB Package Setup
• MOB Packing Station
• MOB Shipping Provider

For each record the saved field values are imported from the intermediate table into the corresponding fields in the MOB tables.

For fields belonging to the Tasklet connectors to Logtrade and ShipIT 365 they are getting new field numbers.

For all other fields it is expected the field numbers are the same as in the corresponding MOS tables.

The used field mapping can be viewed and modified from Mobile Pack & Ship Migration Tool page  by drilling down in the "No. of Field Mappings" fields.:

Image Added

Here you can modify the Destination Field No. or set a checkmark in Ignore Field Value if you need to change the suggestion from the Migration Tool.

After the data restore has imported the field values from the intermediate table, it enables the Pack & Ship feature in the Mobile WMS Setup table.

Why divided in two steps?

The above backup and restore could in some cases be done in one process.

However, it would require table extensions with both the source fields and destination fields being installed at the same time. This would not be a problem for the Logtrade and ShipIT 365 connectors, but we want to make the migration as easy as possible for custom extensions by only requiring our partners do a simple Search and Replace as described in the How-to: Migration of Pack & Ship. It would therefor not be possible access both source and destination fields from custom table extensions at the same time.