Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Code Block
languagedelphi
titleExample 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

 

Image RemovedWindows Handheld Embedded

Image Removed

 

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

 

  

See also

Please note

 

warning


"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

Info
titleExample code in NAV/365BC
  • “Unplanned Count” in Codeunit 
“TF Mobile
  • WMS Adhoc Registr.
"
  • When opening a Receive/Pick/Put-away/Move Order, the warning is performed in Codeunit WMS Order Locking