Versions Compared
compared with
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:
- This will produce a warning, that the user can choose to ignore.
- If the user ignores the warning, the request is Automatically Repeated with a “Force” tag included
- The Force tag tells the backend that the Process can now be completed and NOT halted by the ERROR command.
Example
Code Block | ||||
---|---|---|---|---|
| ||||
IF NOT Force THEN BEGIN ERROR('ForceWarning:' + STRSUBSTNO(MobWmsLanguage.GetMessage('QUANTITY_ERR'),Quantity,ActualQty)); END; |
Info | ||
---|---|---|
| ||
The "Dual dialogue" cannot be avoided when using Windows Embedded |
Existing example of "ForceWarning" in NAV
- “Unplanned Count” in Codeunit “TF Mobile WMS Adhoc Registr."
Info | ||
---|---|---|
| ||
"ForceWarning" feature is supported for example during posting, but not necessarily everywhere elseonly 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 |