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

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 - 

Error After Restore SQL Backup of NAV 2013 Database

Hi all, we are facing a conman issue during restoring a SQL Database backup restored for NAV 2013. While Trying to run object from Object Designer we get below listed error (even the service is configured properly) - --------------------------- Microsoft Dynamics NAV Development Environment --------------------------- There are no NAV Server instances available for this database. You must ensure that a NAV Server instance is running and is configured to use the database before you perform this activity. --------------------------- OK    ---------------------------

Future - What Next After NAV 2016. Code Name - Madeira...

Hi All, While Browsing web I came across some article which says about next release of Microsoft Dynamics NAV. Let's see the History of Code Names Given to Previous Version  - NAV 2013 - Code Name 'Sicily' NAV 2015 - Code Name 'CRETE' NAV 2016 - Code Name 'CORFU' And as we all know that all these are the Islands.