Page Comparison

Order posted successfully.
But error occurred afterwards:
Report 'SomeReport' (ID 1234) is set to print
from a background session (server-side).

This is not supported in Business Central Online. in event: "OnPostPickOrder_OnAfterPostAnyOrder"

The error is caused by custom code that attempts to perform Report.Print() to the printername, which does not exist.

Write code to check the printer name is correct.

Sorry, the current permissions prevented the action.
(TableData Prod. Order Component Read: Base Application)

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

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).

You have manually entered a journal line.

Journal lines should be calculated.

"Whse. Phys. Invt. Journals": ("Directed Put-away and Pick")

Use action "Whse. Calculate Inventory" to generate the warehouse journal lines for counting.

"Phys. Inventory Journals":

Use action Prepare > "Calculate Inventory" to generate the journal lines for counting.

With the release of BC 23.2 Microsoft introduced new validation code on the Warehouse Journal, that resulted in problem with our features, Unplanned Move, Adjust Qty. and Unplanned Count.

Because of Microsoft changes the Error message "Expiration Date must not be changed for an Item tracked by Lot Number." will occur if Location is setup with "Directed Put-away & Pick" and "Skip Whse. Unpl. Count Item Journal Post" disabled.

Extension version 5.45 fixes this

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" 
Remove the value.
-
Fixed in version MOB5.41

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

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 modify code:_
codeunit 6181382 MOB NS Element Management.al

    local procedure GetValueByFieldNo(var RecRef: RecordRef; FieldNo: Integer): Text
    var
        NewFieldRef: FieldRef;
        ValueText: Text;
    begin
        NewFieldRef := RecRef.Field(FieldNo);
        ValueText := format(NewFieldRef.Value());
        exit(ValueText);
    end;

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 webservice created installation has been changed or renamed
• The service must be named "MobileDocumentService"

The 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

1. Registrations were made on Mobile
2. Prod. Order Component Lines were modified in the meantime
3. Orphaned registrations cannot be posted

To resolve the issue:

• Process the Order from BC Webclient
  or
• Delete the "Profiles" folder on Mobile to get rid of any orphaned registrations

• Uninstall and Unpublish "Mobile WMS" extension
• Then re-deploy and Install

If this does not work, then use the Repair-NAVApp command from PowerShell.

Repair-NAVApp -ServerInstance 'MY_INSTANCE' -Name 'Mobile WMS' -Version 5.42.0.0

https://learn.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.apps.management/repair-navapp?view=businesscentral-ps-22