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 52 Next »

Error messages


Error messages are supported everywhere. 


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






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 Cancel or Confirm

    1. Cancel will return the user to the previous screen
    2. Confirm will automatically repeat the result, but this time with a “Force” tag included

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

Example

Below is the XML Request from the mobile device to the backend.

  • Note how a <Force> tag is included.
    • Use this to determine whether to issue the ERROR.
    • If the Force tag is included, do NOT run the ERROR, because this is the second "round trip", telling you that the user selected Confirm
    • See code example below


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

Example 2


Show a Confirmation Dialog when open a Pick and the related Sales Orders has a value in the Work Description Field.

Note that when opening a Document the LockOrder() is always called.


Modify function GetLockOrderNoAndPrefix_FromBackendID in Codeunit WMS Order Locking


Line break

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


See also


Example code in NAV/365BC

  • “Unplanned Count” in Codeunit WMS Adhoc Registr.
  • When opening a Receive/Pick/Put-away/Move Order, the warning is performed in Codeunit WMS Order Locking

An error message


A confirm dialog, using "ForceWarning"




  • No labels