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
Regular debugging 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
Open Business Central
Select ❔ in top right-hand corner.
Select "Help & Support"
Select "Attach debugger to this session"
Start “Regular Debugging” in Visual Studio Code
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 requests in real-time as they are processed.
This is useful when you need to debug for a Commit happens.
This method requires a mobile device to be connected to the environment you are debugging.
Steps
Perform the steps from Attach and Debug-Next section.
Modify the launch.json file:
Delete
sessionId
Change
breakOnNext
to"WebServiceClient"
Start debugging
Wait for the console mesage
Debugger will attach to the next session of type WebServiceClient
Trigger the error from the mobile device