Opening Visual Studio Code from D365 Business Central for Extension Investigation

Modern D365 Business Central extension development is no longer limited to writing AL code from scratch. Microsoft has introduced smarter ways to inspect, investigate, and troubleshoot extensions directly from the Business Central web client by opening Visual Studio Code in context.

This capability is especially useful when developers, consultants, or support teams need to understand how a page works, which fields are used, or why an extension behaves unexpectedly. Instead of guessing, Business Central now allows you to jump straight into Visual Studio Code from the web interface and inspect the underlying AL structure.

Need help with extension investigation or enterprise-level customization?
Our team delivers secure and scalable Microsoft Dynamic 365 Solutions, covering development, debugging, and long-term support for Business Central environments.

What Does “Opening VS Code from Business Central” Mean?

Opening Visual Studio Code from Business Central does not mean editing live production code directly. Instead, it allows you to:

• Inspect page and object definitions

• Download symbols or source (based on permissions)

• Attach a debugger to a running session

• Understand how extensions interact with standard objects

This feature is designed for safe investigation and troubleshooting, especially in sandbox environments.

Who Should Use This Feature?

This workflow is useful for multiple roles:

If you are new to AL development, we recommend first reviewing our detailed setup guide on How to Connect Your Business Central with Visual Studio Code, as this blog builds on that foundation.

Prerequisites Before You Start

Before using the “Open in VS Code” feature, make sure the following are ready:

• Visual Studio Code installed locally

• AL Language extension enabled

• Access to Business Central cloud sandbox or environment

• Proper user permissions

• Internet connection for symbol download and authentication

Without these, the investigation workflow will not function correctly.

Watch Out2sol Youtube Video on Extension Investigation

Step-by-Step: Opening Visual Studio Code from Business Central Web Client

Below are the exact classroom-style steps used in the Out2Sol training video.

Step 1: Search for a Customer

• Use the Tell me what you want to do search

• Type cus

• Select Customer from the results

Step 2: Open Help Pane

• Click the question mark (?) icon in the top-right corner

• The Help pane opens on the right side

• Scroll down

Step 3: Go to Help & Support

• In the Other resources section

• Click Help & Support

Step 4: Inspect Pages and Data

• Locate the Troubleshooting section

• Click Inspect pages and data

Step 5: Page Inspection Pane Opens

• The inspection panel appears on the right

• Displays page metadata, fields, and data sources

This pane is the bridge between the UI and AL code.

Step 6: Explore Page in Visual Studio Code

• Inside the Page section

• Click Explore page in Visual Studio Code

Step 7: Allow VS Code to Open

• A confirmation dialog appears in VS Code

• Allow the AL Language extension to open the URI

• Click Open

Step 8: Inspect the AL Code

• The page source file opens (for example CustomerList.al)

• Scroll through the AL code

• Fields shown in Page Inspection match field() definitions

At this stage, you are inspecting the structure, not modifying live data.

What Actually Opens in Visual Studio Code?

When VS Code launches, Business Central automatically:

• Creates a temporary AL project

• Generates app.json and launch.json

• Downloads symbols or source code (based on permissions)

• Connects to the correct environment

Key Files Explained 

Production Debugging: What You Should Know

Yes, debugging production sessions is possible, but it is controlled.

• You can attach a debugger to a live session

• Source code visibility depends on resourceExposurePolicy

• If source is restricted, only symbols are available

• This prevents unauthorized access to proprietary code

Microsoft designed this to balance power with security.

Common Use Cases for This Feature

• Investigating unexpected page behavior

• Verifying which fields are used by extensions

• Troubleshooting performance issues

• Understanding third-party extension logic

• Learning AL structure from real objects

Visual Workflow Overview

This flow removes guesswork and speeds up analysis.

Common Issues and Fixes

VS Code does not open

• Check AL Language extension

• Verify VS Code installation

• Confirm browser permissions

Source code not visible

• Extension does not allow source exposure

• You will receive symbols only

Debugger not attaching

• Environment mismatch

• Incorrect launch.json values

Why This Feature Matters for Business Central Teams

Extension investigation is no longer limited to senior developers. Microsoft has made it accessible, structured, and safer for broader teams. This improves collaboration between development, functional, and support roles while reducing resolution time.

FAQs

Q. What are the prerequisites for opening VS Code from Business Central?
You need VS Code, AL Language extension, correct permissions, and access to the environment.

Q. Can I debug production environments?
Yes, but access is restricted and controlled by extension policies.

Q. Why do I only see symbols instead of code?
The extension owner has restricted source exposure.

Q. Does this work with cloud sandboxes?
Yes, sandbox is the recommended environment for investigation.

Final Thoughts

Opening Visual Studio Code from the D365 Business Central web client makes extension investigation faster and more practical. It allows teams to move directly from the user interface to AL code, symbols, and debugging tools without breaking workflow.

Used correctly, this feature helps developers, consultants, and support teams understand extensions, trace issues, and work confidently across sandbox and production environments.