Page History

A new Mobile Document Type has been added called "GetLocalizationData"

Make sure you perform point 4.4 "Setup document types" in the installation guide.

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

AL0185, Extension Compilation Failed

[Object] ...does not exist in the current context

[Object] ...for the extension object is not found

[Object] ...is missing

You may be deploying to an unsupported Platform 13 version. See System Requirements BC

Solution: Upgrade to platform 13.5 (BC13 CU5)

failed to compile.Extension compilation failedobjects/Codeunit/Cod81288.MOB%20Common%20Mgt.al(15,32): error AL0133: Argument 1: cannot convert from 'Record TempBlob' to 'var Codeunit "Temp Blob"'

A version of Mobile WMS Compatible with the next release of Business Central has not been deployed to the customers tenant.

https://community.dynamics.com/nav/b/katsonsnavblog/posts/how-to-prepare-your-per-tenant-extension-for-the-business-central-wave-2-update

You need to complete your upgrade.

You might be missing step task 12 in this guide:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrading-the-application-code

This is a symptom that symbols for AL development has not been generated in your database.

Common troubleshooting regarding this topic is very well explained in the following Blog posts:

AL0104, AL0183, AL0198, AL0183

Syntax error, '}' expected
Unexpected character ' '
Expected one of the application object keywords

You are running a BC version earlier than the supported 13.5

Please upgrade to a supported version

You are trying to publish an app to SaaS with the same GUID as our AppSource app.
Only Tasklet can publish an app to SaaS with this GUID.

When installing in SaaS you should simply install via AppSource Marketplace

See also Installation Guide.

Download from http://university.taskletfactory.com/

Receive error: The Bin does not exist. Identification fields and values: Location Code='XXX', Code=''

Populate the Location."Cross-Dock Bin Code" field or disable Location."Use Cross-Docking" for the location.

If you enabled Cross-Docking you must recreate existing Warehouse Receipts (or manually update Warehouse Receipt Lines Cross-Dock Bin Codes) for the location setup change to take effect.

The requested operation cannot be performed in this context

Please check the "Mobile Document Types" setup Page.

Ensure that the correct "Processing Codeunit ID" is set up for the "Document Type "involved in the transaction. (The "Document Type" can be found in the "Mobile Dokument Queue" Page)

Whse. Document No. must be equal to 'Txxxxx'  in Warehouse Journal Line: Journal Template Name=RECLASS,
Journal Batch Name=DEFAULT,
Location Code=WHITE,
Line No.=10000.
Current value is 'HANDHELD'

Remove the number series from the Template Batch.

Go to "Warehouse Journal Templates" 
Select your Templates i.e. "Reclass"

Go to action "Related" > "Template" > "Batches"
Select field "No. Series" 
Removed the value

Getting Reference data failed. Server response: Microsoft.Dynamics.Nav.Runtime.NavXmlCData variable not initialized

You may be posting more than 14 different LotNo/SerialNo/ToBin to the same Warehouse Activitity Line. Renumbering activity lines during putaway posting with SplitLine is not supported until standard BC build 13.5.29483.0 and MOB5.11.

Workaround: Never scan and register more than 14 different LotNo/SerialNo/ToBin at the same orderline at the mobile device at the same time. Instead, register the ~10-14 order lines you have scanned, then repeat to scan the next batch of lines.

Solution: Update to standard application 13.5 (or newer) with MOB5.11 (or newer).

Splitting of purchase lines is not supported by NAV/BC (only one bin can be registered on the mobile device).

Workaround: See You are not allowed to register multiple bins on Receive orders

New Accessor Tables doesn't work on BC 13.0 platform due to FldRef.Value() function working differently on the old platform.

Solution: Either (1) Upgrade to platform 14 (or newer) (2) Upgrade to MOB5.11 (or newer) (3) manually install Hotfix NTW-456.

No document hander is available for Lookup::Attachments.

or

Empty Register Images Reference ID field.

Register Images and Attachment actions are included in Mobile App version 1.5.0+.

But you need Mobile WMS Extension v.5.17+ to use these features.

A call to System.Globalization.CultureInfo.GetCultureInfo failed with this message: Positive number required. Parameter name: culture

You are using Device SL for BC.

We do not sell Device SL. It is something that the partner buys and configures.

Please follow the link for reference to how to set this up: 
https://docs.microsoft.com/en-us/dynamics365/business-central/ui-how-users-permissions
 
Specifically: Look at the sections from The Device License and forward where the setup is outlined.

The default webservice created during Tasklet Mobile WMS installation has been changed or renamed.

Problem was is by not having the standard WMS group and not running the Create Document Types action on Mobile WMS Setup after having created bespoke groups.

Run the "Create Document Types" action on Mobile WMS Setup. 

The server rejected the mobile response.

Increase the "Max message size" on the Service Tier