...
Info | ||
---|---|---|
| ||
Requirements
|
You must review and answer the questions below to request the Migration tool from Tasklet
Do you have any customization created for Pack & Ship?
- No → OK
- Yes → Have you successfully updated your customization as instructed?
- No → You must do it to continue
- Yes → OK
Are you using the ShipIt 365 connector by Tasklet?
- No → OK
- 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?
...
...
- No → You must do it to continue
- Yes → OK
Do you have any customization created for ShipIt 365 connector or LogTrade connector?
- No → OK
- Yes → You need to talk with a developer from Tasklet to verify your customization
Do you understand the how-to migration guide?
- No → Request a meeting with a developer from Tasklet for help
- Yes → OK
Please confirm that you will test the migration in a copy of the production environment to verify the migration result.
- No → Do not start the migration process
- Yes → OK
Technical description of Pack & Ship Migration Tool
...
The contents of this table can be viewed from Mobile WMS Setup page Related → Pack & Ship Migration Tool → Intermediate Table by drilling down in the "No. of Field Values":
Pack & Ship Data Restore
...
The used field mapping can be viewed and modified from Mobile WMS Setup page Related → Pack & Ship Migration Tool → Field Mappingpage by drilling down in the "No. of Field Mappings" fields.:
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.
...
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.