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

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.