In the previous chapter,we discussed, in detail, Microsoft Dynamics 365 Business Central, illustrating its features and the principles for which it was introduced, as well as how it works. In this chapter, we will talk about sandboxes environments, we can use to do the following:
These environments are useful for both Microsoft Dynamics 365 Business Central on-premise and SaaS.
In this section, we will start our discussion on containers, Docker and sandboxes.
Containers are tools that are widely used today because they are based on virtualization that can be used for different purposes. Container provides operating-system-level virtualization, they shares the host system's kernel with other containers. The only limitation to the number of containers that can be used on a machine are memory, the processor, and disk limits.
Docker is a set of tools for creating containerized apps, Docker for Windows is the best way to get started with Docker on Windows systems.
Comparison between virtual machine and Docker technology
Got Docker for Windows? If you have not yet installed Docker for Windows, see https://docs.docker.com/docker-for-windows/install/ for an explanation of stable and edge channels, system requirements, and download and install information. You can visit the page for Docker for Windows...
In this section, we will start by taking a look at sandboxes.
There are two sandbox types that can be used for Microsoft Dynamics 365 Business Central—an online or on-premise sandbox that be managed locally or through Microsoft Azure. There are differences between the two types of sandbox and how they can be used, detailed in the following table.
The following table shows capability comparison:
SaaS sandbox | Local sandbox (container or Azure VM) |
Managed by Microsoft | Managed by a partner |
Uses VS Code only | Uses VS Code, C/AL, and SQL Server |
The production and sandbox is in the same environment | Located in Docker container environments |
Cost—subscription required | Costs—Charged on Azure; free on local |
No database access (backups and load balancing is managed by Microsoft) | Full database access |
Debugging | Debugging |
Visual Studio Code and "In-client" Designer | Visual Studio Code, "In-client" Designer, C/SIDE, and SSMS |
In this chapter, we offered step-by-step instructions on how to install, configure, and activate Docker and sandbox environments for test data, setup, and development in Microsoft Dynamics 365 Business Central and Microsoft Dynamics NAV. Sandbox environments are very useful for developing and testing data and applications before uploading them in a Microsoft Dynamics 365 Business Central SaaS production environment.
Sandbox environments, whether online or in Docker containers, are useful for everyone—customers, developers, and consultants—when studying and testing new product releases. They enable you to create, delete, and recreate products in a very simple way. In addition to Microsoft Dynamics 365 Business Central, Docker and sandboxes are also very useful for older versions of Microsoft Dynamics NAV when simulating upgrades, trying out new product releases, testing new cumulative updates, and so on.
Although this book is now finished, I would like to offer some considerations.
Remember that Microsoft constantly updates and changes its products, so some images and screenshots may not be as up-to-date as possible at the time of reading. The writing mode for this book is in line with my blog posts.
Thank you for reading and enjoy! 'Til we meet next time.
© 2018 Packt Publishing Limited All Rights Reserved
