Description

Use these methods to debug errors that have stopped Mobile Documents from being processed, including for your custom development.

Use the debugger to:

  • View the erroring code and navigate the callstack

  • Set breakpoints before the error occurs

This page only provides an overview. Please refer to the MS documentation.

Prerequisites

Attach to debug is only possible in a Sandbox. Copy your Production environment to a Sandbox as needed

Attach and Debug-Next

Use this method to re-process Mobile Documents with errors.

Steps

  1. Open Business Central

  2. Select ❔ in top right-hand corner.

    1. Select "Help & Support"

    2. Select "Attach debugger to this session"

  3. Start “Regular Debugging” in Visual Studio Code

  4. Use the Mobile Document Queue to Process the document with the error. See Debugging.

Attach and Debug-Next Webservice

Use this method to catch Mobile Documents request real-time as they are processed.

This is useful when you need to debug for a Commit happens.

note

This method requires a Tasklet mobile device connected to your BC environment

This method requires a Tasklet mobile device connected to your BC environment

Steps

  1. Perform the steps from Attach and Debug-Next section.

  2. Modify the launch.json file:

    1. Delete sessionId

    2. Set breakOnNext to "WebServiceClient"

  3. Start debugging

  4. Wait for console mesage Debugger will attach to the next session of type WebServiceClient.

  5. Trigger the error from the mobile device

See also