How to Connect Your Business Central with Visual Studio Code

Welcome to our next class on Dynamics 365 Business Central. Today we will learn how to connect Business Central with Visual Studio Code. This lesson is designed for Dynamics beginners, junior developers, system administrators, and learners who want to build their first AL project in a clean and safe environment. We will explore how the AL Language extension works, what launch.json and app.json mean, and how to run your first sample code inside Business Central.

Before we begin, many businesses ask why this setup is important. In real development projects, you will write AL code inside Visual Studio Code to create custom pages, tables, extensions, fields, and automation workflows. This is the foundation of Business Central development and the starting point of every Dynamics 365 BC project.

If your organization needs help with sandbox configurations, app deployment, or full feature development, our Microsoft Dynamics 365 Solutions team at Out2Sol Global provides complete support from installation to project publishing.

Watch Our Out2Sol Short and Quick Youtube Video

We always start this class by asking our students to watch a short tutorial video.
Here is the same video we used in our training session

Watching it once will make the step-by-step process below easy to follow.

Steps to Connect Visual Studio Code with Business Central

Below are the steps in the same teaching style used in a classroom. Each step is short and clear.

Step 1 Download Visual Studio Code

• Install Visual Studio Code on your computer

• Open Visual Studio Code and wait until it loads fully

• This editor becomes your main workspace for AL development

Step 2 Install AL Language Extension

• Open the Extensions view in Visual Studio Code

• Search for the AL Language extension

• Install the AL Language extension for Microsoft Dynamics 365 Business Central

• This extension prepares Visual Studio Code for AL coding

Step 3 Open Command Palette

• Select View inside Visual Studio Code

• Click Command Palette

• You will use Command Palette often for AL commands

Step 4 Select AL Go

• Type AL Go inside the Command Palette

• Choose AL Go to create a new AL project

• Visual Studio Code generates a starter folder with sample files

Step 5 Select your wave

• Choose the wave that matches your Business Central environment

• In class we select Wave 2

• Select the same wave used by your sandbox for correct compatibility

Step 6 Choose server

• You may choose your own server

• You may choose Microsoft cloud sandbox

• Learners usually work with cloud sandbox because it is pre configured and stable
   

Step 7 Copy application ID or URL

• Open your Business Central application

• Copy the application ID or URL

• You will use this value in your project configuration later

Step 8 Edit launch json

• Open launch json inside the AL project

• Update these fields

  • name

  • tenant

  • environmentType

  • environmentName

  • startupCompany
     

• These values guide Visual Studio Code to your Business Central environment

Step 9 Download symbols

• Open Command Palette again

• Search for the symbols option

• Select the command to download symbols from Business Central

• Symbols allow Visual Studio Code to read pages tables fields and other base objects

Step 10 Update app json

• Open app json inside your AL project

• Update the id field

• Update the name field

• Update the publisher field

• These fields identify your extension inside Business Central

Step 11 Copy the sign in link

• Visual Studio Code shows a link after symbols download

• Copy the link

• Open it in your browser

Step 12 Enter the verification code

• A Microsoft page opens

• Enter the code that appears inside Visual Studio Code

• Select next to continue

Step 13 Sign in to Business Central

• Sign in using your Business Central account

• Authentication completes when your credentials match the environment

• This process connects your AL workspace to the server

Step 14 Confirm the developer connection

• A confirmation page tells you that your developer application is connected

• Close the page and return to Visual Studio Code

Step 15 Edit the Hello World file

• Open the HelloWorld al file

• Change the message from Hello world to Hello to all of Youtube

• This is your first custom AL message

Step 16 Run without debugging

• Select Run without debugging

• The project compiles and publishes to your Business Central sandbox

• Visual Studio Code opens the Business Central web client when the publish completes

Step 17 View your message inside Business Central

• A pop up message appears

• The message displays Hello to all of Youtube

• Select ok

Step 18 Check your extension list

• Open the Extensions page inside Business Central

• Your extension appears in the list

• This confirms that Business Central is connected to Visual Studio Code successfully

Important Notes for Learners

These files are used in every AL project

• launch json

• app json

Launch json controls

• tenant

• environment type

• sandbox name

• startup company

App json controls

• extension id

• extension name

• publisher name

Symbols help Visual Studio Code recognise

• standard tables

• standard pages

• fields

• base application objects

If symbols do not download the environment and Visual Studio Code cannot work together.

Visual Studio Code Business Central Setup Advice

Learners commonly face setup interruptions during the first attempt. You can avoid many issues with a steady approach.

• Always use the correct wave version

• Keep your tenant value accurate

• Use a stable internet connection

• Use the AL extension version that matches your Business Central build

• If you use a sandbox created recently wait for a few minutes before downloading symbols

• Never copy values from another student because tenant values must match your own account

Troubleshooting Common Issues

Here are frequent issues students face in labs.

Symbols do not download

• Wave does not match server version

• Sandbox version recently updated

• Tenant value incorrect

• AL Language extension not updated

Publishing fails

• Incorrect environment type in launch json

• Outdated AL extension

• Incomplete authentication

Login issues

• Wrong account

• Multi factor prompt not completed

• Cached credentials expired
   

Why This Setup Matters

A working Visual Studio Code and Business Central connection supports practical development. All AL code is created and tested inside this environment. You use it for

• pages

• tables

• fields

• automation steps

• small extensions

• custom calculations

This early setup builds the confidence needed for advanced tasks. A clean sandbox environment helps learners experiment safely before touching live data.

Final Notes for Students

After completing this lesson try these small tasks to build confidence

• create a second AL project with a new name

• change the message text in each project

• test symbol download again

• explore the objects inside the base application through Visual Studio Code

• publish your project again and observe the change in the Extensions list

Using these tasks your learning path becomes clear. Learners continue to grow through consistent practice. For teams working with Microsoft Dynamics 365 solutions this foundation prepares the structure needed for future customisation work.