MOBILE WMS

Installation Guide
Dynamics NAV 2013R2 - 2018

Version 4.60
(Last changed March 4th, 2022)
Page 1 of 27

1 Introduction
This document describes how to install the Mobile WMS Dynamics NAV objects and make the basic
configuration to get the solution up and running. When using Microsoft Dynamics NAV the installation will
take about 30 minutes. The top-level steps in the procedure are:

1. Install Microsoft Dynamics NAV (must be done in advance)

2. Import the FOB object file(s)
3. Configure the solution in Dynamics NAV
4. Connect a mobile device (not covered by this manual)

1.1 Pre-requisites
These are the pre-requisites for installing the Mobile WMS solution:

 Access to https://university.taskletfactory.com
Here you can download the Dynamics NAV objects and the related manuals

 Partner Dynamics NAV Developer License

The developer license used to install the Mobile WMS solution must be from a company on the
“Authorized Reseller” list of Tasklet Factory

 Customer Dynamics NAV License

The following add-on modules must be added to the Dynamics NAV license in order to use the
solution
o 6181280 Tasklet Factory Mobile Base
o 6181290 Tasklet Factory Mobile WMS

1.2 Software Dependencies

There are no dependencies. The solution will work with any service pack of Dynamics NAV.

1.3 Dynamics NAV License Dependencies

The Mobile WMS solution can be used with any Dynamics NAV license, but some features can only be used
if the Dynamics NAV license includes access to those features. An example of this is the “Warehouse
Receipt” document. If the document can be created in NAV then it will show up on the mobile devices. If
not, the customer will typically work directly on the purchase order document.

Tasklet Factory |www.taskletfactory.com

Page 2 of 27

2 Microsoft Dynamics NAV Installation

It is assumed that the details of how to install the different components of Microsoft Dynamics NAV are
known by the reader and completed before the Mobile WMS installation is performed. This chapter only
mentions the things to check after making a standard installation.

When using Microsoft Dynamics NAV the mobile devices communicate through the standard Microsoft
Dynamics NAV web services. Please make sure that the NAV web service is enabled:

If android devices are used, please make sure, that “Use NTLM authentication” is checked.

Note: You can get help for setting up web services here:
http://msdn.microsoft.com/en-us/library/dd355036(v=nav.100).aspx

Tasklet Factory |www.taskletfactory.com

Page 3 of 27

3 Install Mobile WMS

This chapter explains how to import the Mobile WMS objects and make the basic configuration. You need
the FOB files containing the Mobile WMS objects to complete the installation. The object files used in the
installation are delivered in multiple versions to make the import procedure as easy as possible.

Each file exists in FOB or TXT format

The TXT version can be split into a file for each object if you want to make a text compare with the object to
be replaced. There are multiple tools available on www.mibuso.com

 All objects
This file contains all objects in the solution

 Changed standard objects

Contains only the standard Microsoft Dynamics NAV objects that were modified to support the
Mobile WMS solution. These objects are rarely imported directly because there is a high risk that
the objects being replaced will have country specific modifications and possible customizations
made by the Dynamics NAV partner

 Mobile WMS objects only

For new installations this file can safely be imported. It only contains Mobile WMS objects

 Changes in this version

This file contains the objects that were changed compared with the previous official release.
Use this file if you are performing an upgrade.

3.1 Recommended approach for new installation with Existing customizations

1. Import the Mobile WMS objects only FOB

2. Manually apply the changes to the standard NAV objects

The changes needed are documented in the following sections. Remember to update the version
list of the standard NAV objects to show that they have been customized for the Mobile WMS
solution. The documentation trigger must also be copied.

Tip: If you have a NAV system where the changes have been applied already you can copy / paste
between the reference and target systems. This is especially handy when adding fields because all
properties are copied as well.

3. Compile all changed objects

Set a filter on the version list: “*MOB*” and compile all objects.

3.2 For a new installation with No customizations

1. Import the All objects only FOB

2. Compile all changed objects

Set a filter on the version list: “*MOB*” and compile all
Tasklet Factory |www.taskletfactory.com
Page 4 of 27

3.3 Objects
The Mobile WMS solution consists of the following objects. There are very few changes to the standard
objects. These changes are documented here.

Note: The standard objects are exported from RTM version.

Unless the target system has the exact same version it is recommended to manually implement
the changes to the standard objects.

3.4 Changed Tables

The changes to the standard objects are documented in the documentation trigger.

 27: Item
Added field to identify whether an Item has changed.

Documentation trigger:
Tasklet Factory - Mobile WMS
Added field "Last Time Modified"

Version List
Add MOB4.04 to the end of the version list

 32: Item Ledger Entry

Enabled the key on Serial No.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Enabled the key on Serial No.
Version List
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 5 of 27

 83: Item Journal Line

Added the field RegisteredOnMobile. It shows if the counted value has been set from a mobile
device.

Added a key on: Location Code, Bin Code, Item No., Variant Code

Documentation trigger:
Tasklet Factory - Mobile WMS
Added the field RegisteredOnMobile
It shows if the counted value has been set from a mobile device

Tasklet Factory - Mobile WMS

Added key "Location Code","Bin Code","Item No.","Variant Code"
It is used to sort the count order lines on the mobile device

Version List
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 6 of 27

 233: Item Journal Batch

Added the ReleasedToMobile field. It determines if the journal batch is available on the mobile
devices.

Documentation trigger:
Tasklet Factory - Mobile WMS
Added the ReleasedToMobile field
It determines if the journal batch is available on the mobile devices

Version List
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 7 of 27

 337: Reservation Entry

Enabled the keys on Serial Number and Lot Number.

Added Text50 field “Prefixed Line No.”

This field is used when integrating directly to transfer orders that handle items with item tracking
enabled.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Enabled the keys on Serial Number and Lot Number.
- Added the "Prefixed Line No." field. This is used when the mobile application integrates directly
to transfer orders that handle item tracking information.

Version List
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 8 of 27

 5767: Warehouse Activity Line

Added boolean field "LineSplitAutomatically". This field is used by the automatic split functionality
when posting warehouse activities to multiple bins.

Documentation trigger:
Tasklet Factory - Mobile WMS

Tasklet Factory - Mobile WMS

Added boolean field "LineSplitAutomatically"
This field is used by the automatic split functionality when posting warehouse activities to multiple
bins

Version List
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 9 of 27

 7310: Warehouse Journal Batch

Added the ReleasedToMobile field.
It determines if the journal is visible on the mobile device.

Documentation trigger:
Tasklet Factory - Mobile WMS
Added the ReleasedToMobile field
It determines if the journal is visible on the mobile device

Version List
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 10 of 27

 7311: Warehouse Journal Line

Added the RegisteredOnMobile field. This field is set when a counted quantity has been updated
from the mobile device.

Documentation trigger:
Tasklet Factory - Mobile WMS
Added the RegisteredOnMobile field
This field is set when a counted quantity has been updated from the mobile device

Version list
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 11 of 27

3.5 Changed Pages

Standard
 262: Item Journal Batches
Show the ReleasedToMobile field.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Show the ReleasedToMobile field

Version list
Add MOB4.00 to the end of the version list

 392: Phys. Inventory Journal

Show the RegisteredOnMobile field.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Show the RegisteredOnMobile field

Version list
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 12 of 27

 7326: Whse. Phys. Invt. Journal

Show the RegisteredOnMobile field.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Show the RegisteredOnMobile field

Version list
Add MOB4.00 to the end of the version list

 7329: Whse. Journal Batches List

Show the ReleasedToMobile field.
Set page property Editable to Yes.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Show the ReleasedToMobile field
- Set page property Editable to Yes

Version list
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 13 of 27

 7336: Whse. Shipment Subform

Show the ToteIDs field, added WMS codeunit.

Documentation trigger:
Tasklet Factory - Mobile WMS
- Added the ToteIDs field and the MobWMSToolbox variable

Version list
Add MOB4.00 to the end of the version list

Tasklet Factory |www.taskletfactory.com

Page 14 of 27

4 Basic configuration

4.1 Mobile Menu

The “Mobile WMS” menu contains links to relevant setup Pages and NAV features that integrate with
Mobile WMS.

Tasklet Factory |www.taskletfactory.com

Page 15 of 27

Tasklet Factory |www.taskletfactory.com

Page 16 of 27

4.2 Web service configuration

The web service configuration is completed by executing action “Setup Web Service” from the page
“Mobile WMS Setup”.

The Action will create the relevant entry in page 810 (Web Services)

The SOAP URL should be delivered to Tasklet Factory Support, in order to create the configuration packets
for the mobile devices.

Tasklet Factory |www.taskletfactory.com

Page 17 of 27

4.3 Setup mobile messages

Create mobile languages and messages (translations) for all supported language codes.

Messages are created for English, German and Danish.

Open the “Mobile WMS Setup” Page and click Actions -> “Create Messages for all languages”

4.4 Setup document types

The document types define the interface towards the mobile devices.

Think of the document type as a function being called from the mobile device.

Open the “Mobile WMS Setup” Page and click Actions -> “Create Document Types”

This creates the standard document types used by the Mobile WMS solution and assigns the “WMS” group
to all of them.
Tasklet Factory |www.taskletfactory.com
Page 18 of 27

4.4.1 Mobile Group

Also created is the Mobile Group “WMS”. This is normally the only group needed.

 The Mobile Group specifies

o Which Users can access the Groups functions
O Which Main Menu Items are available on the mobile device

Tasklet Factory |www.taskletfactory.com

Page 19 of 27

4.4.2 Mobile Menu

The menu on the mobile device is controlled from NAV. Each group can have a different menu that only
shows the relevant features. The standard configuration gives access to all available menu items. Please
remove the unwanted items before use.

Tasklet Factory |www.taskletfactory.com

Page 20 of 27

4.5 User Permissions

The function “Create Document Types” also creates a permission set “TF-MOBILE-USER” that contains
relevant permissions for using a mobile device. The permission set contains permissions to Mobile WMS
tables and standard NAV tables, that are not contained in the recommended permission sets.

The recommended permission sets that should be allocated to each mobile device user in order to perform
processes available from the mobile device are:

The permissions must revised when modifications to standard NAV or Mobile WMS objects are
implemented.

Tasklet Factory |www.taskletfactory.com

Page 21 of 27

4.6 Mobile Users

All users of the mobile devices must be created as mobile users first. This is done using the “Mobile Users”
Page.

The “User ID” is selected from the users created in NAV. When the users are added they must be assigned
to a group.

For each user of the mobile device a language code can be specified.

Tasklet Factory |www.taskletfactory.com

Page 22 of 27

4.7 Language Setup

The language handling of Mobile WMS the consist of 3 areas:

1. Device Languages
Many languages supported, see below

2. Messages Language
a. English
b. German
c. Danish

3. Other/Mobile Messages from NAV

4.7.1 Set up Device Language

The device language is used by to generate the language for the mobile application front-end.

 For each “Mobile Language” a “Device Language” can be specified.

 “Map” the NAV language code i.e. DEU to “DE” etc. according to the table below

The following device languages are supported by the Mobile WMS application by default. Others may be
available on request.

4.7.2 Set up Message Language

All messages generated from Mobile WMS to the mobile device are represented by a message code.

Tasklet Factory |www.taskletfactory.com

Page 23 of 27

For each message code a set of translation records can exist – one for each language. If a language code is
not specified for a user or a message code is not existing for a message code, Mobile WMS will use English
(ENU).

The function “Create Messages” creates a set messages for the selected language code.

Mobile WMS offers messages for English, Danish and German.

 If the selected language code is ‘DAN’ messages are created in Danish.

 If the selected language code is ‘DEU’ messages are created in german.
 Otherwise messages are created in English ‘ENU’.

4.7.3 If other translations are needed,

A custom set of messages can be created for eg. ‘CSY’.

 Export the created messages in English

 Translated
 Re-imported by using “RapidStart Services”

4.7.4 Messages from standard NAV

All standard NAV messages (eg. errors during postings) are sent ‘As-Is’ to the mobile device, and will use
the language specified in NAV setup.

NOTE: Confirm dialogs are not supported by web services and will generate an error on the mobile device.

Tasklet Factory |www.taskletfactory.com

Page 24 of 27

4.8 Mobile WMS Setup

Before the mobile devices can be used the “Mobile WMS Setup” screen must be reviewed.
Here the general behaviour is configured.

Here is an explanation of each field:

General
 ”Sort Order Pick”
This setting controls the sort order of pick orders. There are 3 options:
- Worksheet
- Item
- Bin
If work sheet is selected the order lines are sorted in the sequence defined when the order was
created. A typical usage of this is to sort the lines according to bin ranking.

 ”Sort Order Put-away”

Same as for Pick.

 ”Sort Order Movement”

Same as for Pick.

Tasklet Factory |www.taskletfactory.com

Page 25 of 27

 “Move Whse. Jnl. Template”

This template is used to post unplanned movements from the mobile device. The template is only
used if the location where the unplanned move is performed is configured to use “Directed Put-
away and Pick”.

 “Unplanned Move Batch Name”

This name is used for the journal batch when the unplanned move is posted from the mobile
device.
The standard value to use is MOB_UPM. The name is only used if the location where the unplanned
move is performed is configured to use “Directed Put-away and Pick”.

 “Move Item Jnl. Template”

This parameter is used by the Bulk Move feature

 “Unpl. Item Jnl. Move Batch”

This parameter is used by the Bulk Move feature

 Use Base Unit of Measure

If this check mark is set all quantities on the mobile device must be entered in the base unit of
measure.
If it is not set the quantities are entered in the unit of measure used on the order lines in NAV.

Tasklet Factory |www.taskletfactory.com

Page 26 of 27

 Enable Tote Picking

If this check mark is set you will be able to pick multiple orders for multiple customers at the same
time by scanning boxes to connect with the orders/customers.

 Tote per
This setting termins how the orders are connected with boxes. There are 3 options:
- Destination No.
Tote per customer

- Source No.
Tote per order

- Whse. Document No.

Tote per shipment

Count
 “Inventory Journal Template”
Select the journal template that is used for physical inventory journals.
The standard value is PHYS. INV.

 “Whse Inventory Jnl Template”

Select the journal template that is used for warehouse physical inventory journals.
The standard value is PHYSINVT

 “Unplanned Count Warning”

This flag controls if the user should be warned when the unplanned count feature is used. If the
warning is enabled the user will get a warning if the physical quantity exceeds the tolerance levels
defined below.

 “Count Warning Tolerance %”

If the physical quantity exceeds this tolerance level the user will get a warning on the mobile
device.

 “Count Warning Min. Tolerance”

The minimum tolerance prevents warning messages on items with a large difference in
percentages, but only a small numerical difference. The difference must exceed this value before
the warning is generated.

 “Sort Order Count”

Controls the way the count order is presented.

 “Skip Whse. Unpl. Count Item Journal Post”

If – and only if - the location uses “Directed Put-away and Pick”, this flag makes it possible post the
warehouse entries generated by the unplanned count and adjust quantity, without posting item
journal. Periodically “Calculate Whse. Adjustment” from an Item Journal must be executed and
posted.

Tasklet Factory |www.taskletfactory.com

Page 27 of 27

5 Uninstall Procedure
The Mobile WMS solution can be uninstalled by deleting all Dynamics NAV objects in Tasklet Factory’s ISV
range and manually remove the changed objects described in section 3.

The objects to delete / modify can be found by applying the “*MOB*” filter to the version list in the object
designer.

If the version starts with “NAV” it is a standard object and must not be deleted. The ID of the object also
indicate this.

6 Backup Procedure
There are no special backup procedures for the solution

Tasklet Factory |www.taskletfactory.com