Skip to main content

Business Central 2022 release wave 1 - Docker Preview Environments.

Hi Readers,

Yes the future version of Business Central is about to release in April.

But as developers we need access to Next version to be ready for what's changing and how our App Source Extensions and Per Tenant Extension will be impacted with Next Release.

Microsoft have already released Preview Features of Business Central 2022 Release Wave 1.

We can setup docker containers for next releases or create Sandbox for SaaS Customers to Test and Learn new features.

Why Should ISV setup Preview Environments? 

  • ISV need to check compatibility of Extensions with the next release.
  • If any changes are required for ISV Extensions, then they should be fixed before actual release.
  • Updated Release is Submitted to Microsoft for AppSource Validation.

Why Should Partners Setup Preview Environments?

  • All PTE's Need to be Reviewed for compatibility issues with next release.
  • If any changes are required, then those changes should be completed and deployed on Preview Environment.
  • Customers can test those changes (if any) in Preview Environment. 

Why Extensions will not be compatible?

  • As we all understand now that Microsoft is enhancing features in product in every release.
  • As these features are introduced / enhanced,  some of the legacy features have to be dropped / deprecated. 
  • Microsoft is announcing and providing all insights on how to rewrite these code segments to support the new enhanced with every release.
  • Every Developers gets a warning and other signs in VS Code when they are trying to utilize a feature / object which will no longer be supported in future.

How to Setup Docker Preview for SaaS Environment?

You can generate Docker Build Command using New-BcContainerWizard (read here) and then change artifactUrl parameter.

 The ArtifactUrl for preview environment require a separate storageaccount as shown below.

Get-BcArtifactUrl -storageAccount BcPublicPreview -type 'Sandbox' -country 'us' 

You can change country & type (Sandbox & OnPrem) based on your requirement.

Hope this article helps you to setup the Public Preview of Business Central 2022 Wave 1.

If you have questions please add comment to this article.

Saurav Dhyani


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 - 

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.

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.