Description
| Excerpt | ||
|---|---|---|
| ||
You can use the Mobile Document Queue List to handle and inspect failed mobile documents. |
Finding the right mobile document
Isolate for the right entry, using columns like Document Type, Registration Type or Status Filters
View Error Message and Call Stack
The Response XML contains both the Error message and Error call stack.
How to interpret the Error Call Stack
The beginning of the error call stack is where the process failed. This allows you to:
Isolate the source of the erroneous code
Identify where to set breakpoints for debugging, see https://taskletfactory.atlassian.net/wiki/spaces/TFSK/pages/745308161/Debugging+in+Business+Central
Third-party applications can be the cause of the error
The call stack can point to non-MobileWMS extensions. Look for "ExtensionName by Publisher".
This points to an issue outside of Mobile WMS. In Example, the Error Call Stack points to the Extension ShipIT 365 by IDYN B.V.
Share the Error and Call Stack with Tasklet
| Tip |
|---|
You can copy these files to the ticket if you have an ongoing Service Desk ticket and have trouble pinpointing the root cause of the Error. |
Download the XML
Select Document > Show Request XML
Save the file
Select Document > Show Response XML
Save the file
How to Reprocess Mobile Documents
You can reprocess failed mobile documents from the Mobile Document Queue List in Business Central.
This will show the error message on your screen.
Note: The code is executed in the context of the current user
Select Process > Process Document
Use “Copy Details” to view more additional information
When reprocessing fails, you will see the error on the screen.
More information is available in Copy details.
Select "Copy Details"
Paste the text to a text editor or an ongoing Service Desk ticket if you have trouble pinpointing the root cause of the Error.
How to interpret Request XML
The mobile app request is likely the most interesting for development. The request shows the values available.
Here are fields "MyDate", "MyText" available in a request for an Unplanned Function named "MyUnplanned".
|