Skip to main content

How to Setup Business Central 2019 release wave 2 Preview?

Hi all,

In the last article, we discussed that Business Central 2019 Release Wave 2 Preview is available to download via Dockers.

If you as a partner have access to Microsoft Collaborate "Ready To Go" program then follow steps below.

Step 1 - Update your ContainerHelper to

Open Powershell (64-bit client), as shown below.
Please don't use the 32-bit client (x86).

Run command to install Container Helper - Install-Module -Name navcontainerhelper -Force

Step 2 - Create a new container using powershell command as below.

$imageName = ""
$containerName = "<ContainerName>"
$auth = "UserPassword"
$credential = New-Object pscredential '<admin>', (ConvertTo-SecureString -String '<Password>' -AsPlainText -Force)
$licenseFile = "<licensefile>"

New-BCContainer -accept_eula `
                -imageName $imageName `
                -containerName $containerName `
                -auth $auth `
                -credential $credential `
                -licenseFile $licenseFile `
                -updateHosts `
                -includeAL `
                -memoryLimit <3G>

Change Parameters which are highlighted in Red
<ContainerName> - Name of Container that you want to assign to the container.
<admin>      -- UserName to Login in container.
<Password-- Password to Login in container.
<licensefile> -- Path of License file in your local machine.
<3G>             -- Memory that you would like to allocate to Docker Container.

Step 3 -  Container Ready.

In a few minutes to hours based on how much you use dockers, containers should be ready. At this point, PowerShell cmdlet may error out and ask you to authenticate before execting Powershell scripts.

The Authorization command should be something like -
docker login "" -u "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -p "xxxxxxxxxx"

After the command is completed system will generate a message and details as below. Once completed please save details for future use.

Step 4 - Login to Client.

Web client 😋, as there is no more any Windows client and Development Environment with next release.

As you can see its a Sandbox environment as shown below.

Step 5 - Check Installed Extension.

Open Extension Management Page to see how many extensions are installed. If you don't know you will see two extensions BaseApp and System Application.

With this version, base Microsoft is also as an extension.

Step 6 - Download the VSIX.

Download file from the URL that we have as a result of Docker Creation message in Step 2.

Once Downloaded Install that VSIX File from VS Code  Extension Menu as shown below.

Step 7 - Create a New Extension.

Create New Extension using AL:Go!

You will be prompted with a new window to select Target Platform. Select 4.0 from the menu.

Select Your Server in the next selection and key in username and password that you specified while generating  Docker container step 2.

The system will generate launch.json and you will see a file like below.

Step 8 - Check Dependencies for the Extension.

Open App.json and you will see new parameters with values.

  • Platform - which is for next release.
  • Dependency 1 - Base Application with version
  • Dependency 2 - System Application with Version

And three files in .ALPackages - 
  • Microsoft_System

Step 9 - Verify table names in SQL.

If you login to SQL Server from Dockers and expand Table names in the database you will see all Microsoft base app are with extension ID as highlighted below.

In example Base App Extension ID is  "437dbf0e-84ff-417a-965d-ed2bb9650972"

Hope this article helps you to setup Wave2 docker container.

Let me know your views on this article as a comment.

Saurav Dhyani


  1. where do you get the license file?

    1. @Rashed Amini - You can use Business central 13 or BC 14 license.

  2. Do you need an Azure account for this installation? Because when I try to pull the image it says that I need to login to which redirects me to the Azure account creation page.

  3. Hi Saurav,

    first of all thanks for the document, all were smooth, but need more brief on "Step 9 - Verify table names in SQL"
    can you please help me with how to open Docker SQL management.

    Thanks in Advance !

    1. Hi Sachin,
      Thanks for the comment.
      You can use your local SQL Server Management studio.
      In Server name you can specify the Docker container name and use username and password that you used for creating container.
      That will allow you to access SQL Database.


Post a Comment

Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.