How To Connect To A Named Sandbox Environment

How To Connect To A Named Sandbox Environment

Darren Austin

Lead Dynamics Business Central Developer|Kerv Digital

Published 06/07/22 under:

Have a question?

Get in touch

You’ll often find you need to connect visual studio code to each of the sandbox environments you’re working with…

As a developer working across multiple projects you’ll find that you need to connect visual studio code to each of the sandbox environments you’re working with.

The standard launch .json file won’t work when you initially start your project as its generic – expecting you to only connect to one project and the account you’re connecting with is not a partner account – it’s a user account.

Connecting to the sandbox from Visual Studio Code is key for your application as you’ll need to download symbols – this gives you the symbols from the base Microsoft apps but also you can extend the app .json file to include any custom apps you need in your project.

To connect to a named sandbox instance, I have found adding the following lines in to your launch json file:

  1. Server – this is the http url of your server – Not 100% needed in this process but I like to add it to see the full detail of what I am connecting too.
  2. Tenant – this specifies the tenant name of the server, in my example it is the guid you would find in your full business central url.
  3. SandboxName – This is the name of the sandbox it should publish too, this is key if you have multiple sandboxes in your tenant.

 

 

As an end result your file should look something like this, having added these lines and saving the file.

You should be able to download symbols and publish your applications to your sandbox environment.

 

 

If you have multiple sandbox environments in your tenant, then you should only have to change the last property – SandboxName – to the name of your sandbox.

Download symbols and then just publish

Related Articles

You might also be interested in

From our world to yours

Casting An Eye On A CoE

From our world to yours

Growing Our Group Capabilities with Monochrome Consultancy

From our world to yours

Uncovering Unconscious Bias

From our world to yours

Life @ Kerv Digital As A Solution Architect

From our world to yours

CX & EX Reimagined: Driving customer loyalty and employee wellbeing through Genesys...

From our world to yours

Facilitating Your Finance Department With Business Central

From our world to yours

Artificial Intelligence: The Dawn Of A New Era

From our world to yours

6 Benefits of Managed Security Service Providers

From our world to yours

Kerv Digital Events: Microsoft Cloud For Nonprofit Live Demo

From our world to yours

Kerv Digital SNT 2023

From our world to yours

All About Automation

From our world to yours

Life @ Kerv Digital As A Business Central Support Consultant

From our world to yours

Why the SLA isn’t enough – what really matters when choosing an...

From our world to yours

Accelerate your communications compliance with MS Teams

From our world to yours

What Makes a Good Managed Service Provider

From our world to yours

A Deep Dive Into Data Science

From our world to yours

Life at Kerv as a Commercial Director

From our world to yours

The Importance of Sustainability and the Changes We Need to Make

From our world to yours

Decision Making Problems & How To Navigate Them

From our world to yours

Microsoft Cloud For Nonprofit: Campaigns

From our world to yours

Email vs Messaging: The Search for a Better Customer Experience

From our world to yours

Life @ Kerv Digital As A Full Stack Developer

From our world to yours

Microsoft Cloud For Nonprofit: Volunteers

From our world to yours

A Kerv Digital & Firebrand Training Success

From our world to yours

Going Beyond The Theory: Kerv Digital & The DVSA

Have a question?

Leave your details and a member of the team will be in touch to help.

"*" indicates required fields

By pressing send, you agree to our Terms and Conditions and Privacy Policy.
This field is for validation purposes and should be left unchanged.