Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

1: Error messages

 

Error messages are supported everywhere. 

 

Simply perform the “ERROR()” command in NAV and the message will be shown on the scanner.

 

 

 


 

2: Warning/Confirmation/Message

 

When a warning is wanted, the string ”ForceWarning” can be prefixed to an Error message.


The process flow is:

  1. This will produce a warning, that the user can choose to ignore.

  2. If the user ignores the warning, the request is Automatically Repeated with a “Force” tag included

  3. The Force tag tells the backend that the Process can now be completed and NOT halted by the ERROR command.


 

Example

Example in NAV/BC
IF NOT Force THEN BEGIN
  ERROR('ForceWarning:' + STRSUBSTNO(MobWmsLanguage.GetMessage('QUANTITY_ERR'),Quantity,ActualQty));
END;

 

Line break

Line breaks / Carriage Return, can be performed by using the "\" character in NAV/BC.

 

 Android

 

Windows Handheld Embedded

 

The "Dual dialogue" cannot be avoided when using Windows Embedded

 

 

 

Please note

 

"ForceWarning" feature is only supported on the initial answer sent to the mobile device.

So in OrderLines scenario, the warning is done in Codeunit TF Mobile WMS Order Locking

Example code in NAV/365BC

“Unplanned Count” in Codeunit “TF Mobile WMS Adhoc Registr."

 

 

  • No labels