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 55 Current »

Description

You can use the Mobile Document Queue List to handle and inspect failed mobile documents.

Finding the right mobile document

  1. Open Mobile Document Queue List

  2. 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.

image-20241216-125518.png

How to interpret the Error Call Stack

The beginning of the error call stack is where the process failed. This allows you to:

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.

image-20241216-131017.png

Share the Error and Call Stack with Tasklet

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

image-20241216-134125.png

  • 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.

  1. Select "Copy Details"

  2. Paste the text to a text editor or an ongoing Service Desk ticket if you have trouble pinpointing the root cause of the Error.

image-20241216-122619.png

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".

<?xml version="1.0" encoding="utf-8"?>
<request name="PostAdhocRegistration" created="2020-02-14T15:24:24+01:00" xmlns="http://schemas.microsoft.com/Dynamics/Mobile/2007/04/Documents/Request">
  <requestData name="PostAdhocRegistration">
    <MyDate>14-02-2020</MyDate>
    <MyText>2</MyText>
    <MyDecimal>4</MyDecimal>
    <MyDateStep>14-02-2020</MyDateStep>
    <MyTextStep>2</MyTextStep>
    <MyDecimalStep>4</MyDecimalStep>
    <RegistrationType>MyUnplanned</RegistrationType>
  </requestData>
</request>

  • No labels