Attach AL debugger to active session or next session

  • Article

Important

This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.

Enabled for Public preview General availability
Admins, makers, marketers, or analysts, automatically Apr 4, 2023 Apr 4, 2023

Business value

The legacy C/AL debugger supported attaching to an existing session or to the next session for a specific user. While this has been possible with the AL snapshot debugger for some time, the standard, more powerful AL debugger in Visual Studio Code is still missing this capability, and it's been a partner ask to fill this gap for a while. With the introduction of service-to-service (S2S) authentication, this has become more important, since it's now much harder to debug important web service scenarios, which are only possible with snapshot debugger.

Feature details

Just as with the snapshot debugger, attach the AL debugger to either an existing running session or to the next session for the specific user. In both cases, this is set up by specifying a session ID or a user ID in the launch.json attach configuration.

In addition, a new "Attach Debugging" PermissionSet is available to allow cross-user debugging.

Use launch.json to attach to specific session ID or next session for specific user ID

Tell us what you think

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.

See also

Attach configuration (docs)