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

Problem

You get a runtime error on mobile with an error message from Business Central.

Solution

Step 1: Is it a known error message

See Error Messages

Step 2:  Inspect the Callstack

The call stack points to the failing code, which is VERY helpful.


The error can originate from several sources:

  • Base BC code
  • Standard Mobile WMS code
  • Partner Extension code


The call stack is included in the error XML response and can be seen in the Mobile Document Queue.

The Request and Response -XML also tells you what data is being exchanged between Mobile and BC.


Step 3:  Has the system been updated lately

  • Has Mobile WMS extension been updated?
  •  Have you changed any extension code?
  • Has Business Central been updated?

  • Have you changed how the system is set up?

Step 4: Is it isolated to one order?

  • Is it a single document that cannot be processed?
  • Can you reproduce the issue by creating new documents? (Using a sandbox, step 3)


Step 5: Create a "Sandbox" copy of the production

With a sandbox you can:

  • Avoid disrupting the customer's business
  • Change data to check whether the issue changes
  • Dis-/enable extensions and check whether the issue changes
  • Debug code

See also



  • No labels