The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Business Central Debug on different Sandboxes
Someone asked me for info on how to debug in the sandbox in a SaaS environment, where there are more than one sandbox.
The thing is simple, but sometimes it happens that an error is returned when there are more Sandboxes; in this case, it is necessary to connect to the correct tenant and sandbox, otherwise the VS code connects to the Default sandbox and we may be able to publish an extension but not be able to debug.
Example of Configuration
Two Active Sandboxes in this scenario
#1 – Access to Default “Microsoft Cloud Sandbox”
“name”: “Microsoft cloud sandbox”,
#2 – Access to a “Selected Sandbox”
“sandboxName”: “Sandbox14”, //SANDBOX NAME
“tenant”: “XXXX-XXXXXXX-XXXXX-XXXXX” //TENANT ID
#3 – CHECK THE DIFFERENCES
“sandboxName”: “Sandbox”, //SANDBOX NAME
“tenant”: “xxxxxx-xxxx-xxxxx-xxxxx” //TENANT ID
With this configuration you can Publish and Debug on your selected Sandbox.
Business Applications communities