Skip to main content

Preview environments for Business Central 2021 release wave 1.

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 released the Preview Environments for #msdyn365bc 2021 Release Wave 1. 

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

IMPORTANT: A few known issues – still pending to release in preview

  • Deploying extensions from Visual Studio Code with install or upgrade code units fails on cloud sandboxes:
    • There is a current issue with permissions when trying to deploy and execute install and upgrade code from Visual Studio Code to a cloud sandbox. This will also imply that this code cannot be debugged. Mitigation in preview is deploying through extension management page or working on a docker container.
  •  A number of high impact report extension fixes are not in the preview:
    • These include that using dataitem columns with quoted names with spaces will result in runtime resolve errors, that triggers in request pages and the report extension itself are not working, that attempting to use CurrReport.Quit in a report extension results in a crash, and that referencing local variables in request page extension triggers or procedures raises error diagnostics.
  • Permissionsets are not working properly in Docker
    • The new permission system is disabled by default in RC1. When running in Docker you might need to add this parameter if you are logging on as anything but SUPER: -additionalParameters @("-e customnavsettings=UsePermissionSetsFromExtensions=true")
Steps To Setup Docker Container For BC 18 Preview - 

Open PowerShell and run below command, after updating path of your Development License. 
(Line No. 5)

$containerName = 'bc18preview'
$credential = Get-Credential -Message 'Using UserPassword authentication. Please enter credentials for the container.'
$auth = 'UserPassword'
$artifactUrl = Get-BcArtifactUrl -storageAccount BcPublicPreview -country 'us' -type 'Sandbox'
$licenseFile = 'C:\Dev.flf'
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -multitenant:$false `
    -assignPremiumPlan `
    -licenseFile $licenseFile `
    -dns '8.8.8.8' `
    -memoryLimit 4G `
    -updateHosts


Enter username and password that you would like to use for docker.

After sometime, the docker environment will be ready for testing as shown below.


Hope you learn with the new release via docker.

If you are using BC SaaS then you can create new sandbox with Preview Version as shown below.


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

If you have questions please add comment to this article.

Regards,
Saurav Dhyani

Comments

  1. if we include "includeTestToolkit" parameter to command, it gives error while publishing Microsoft_Tests-ERM_18.0.23013.23320.app

    ReplyDelete
    Replies
    1. That correct based on memory and execution time.
      That is the reason I create container without test toolkit and later add test toolkit separately using Import-TestToolkitToBcContainer.

      Delete

Post a Comment

Popular posts from this blog

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.

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.