Description
Use the Mobile Document Queue List to inspect the XML data being sent to and from the Mobile devices. Error Call Stacks can be found here.
Use Case
View XML values and know whether AL code has taken effect
View Error Call Stack
Share this information with Service Desk
See Mobile Document Queue List for details about Request/Response XML.
View and Download Request/Response XML
Step 1:
Open the Mobile Document Queue List.
You can now see the XML on-screen and search using the browser "Find function" (CTRL+F).
Step 2:
Download the XML.
Select the correct mobile document.
Select Document > Show Request XML
Save the file
Select Document > Show Response XML
Save the file
Example of Request XML
The request is likely most interesting for development. The request will give you an overview of which values are available to you and what they are named.
Here are a number of fields i.e. "MyDate", "MyText" visible in a request for an Unplanned Function named "MyUnplanned".
Request example
<?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>
View Error Call Stack and Debug
See Debugging.
When a request ends in Status: Error, it will remain so until it succeeds. Subsequent attempts from mobile will only attempt to re-process this original request.
You can use this to inspect the Call stack and initiate debugging.
Go to the "Mobile Document Queue"-page.
Select the latest Document with Status = Error
Select Document > Show Response XML
orSelect Process > Process Document
You can also re-run the process and get the error on the screen
Select Process > Process Document
Select "Copy Details"
Paste the text into a Text Editor like "Notepad" (Ctrl+V)
External code unit
If the call stack points to non Tasklet code unit e.g. connector, you can look for the publisher after the "-" sign - example below "ShipIT 365 by IDYN B.V."