Skip to main content

MSDYN365BC SaaS - How Do I Setup Preview Sandbox for BC 2020 Wave1?

Hi Readers,

As most of us were aware of it that Microsoft has released Preview Sandbox for Business Central SaaS Environment.

So if you are using Business Central (SaaS) its time to setup your Preview container to Test your Per-Tenant Extensions.

If there are issues in those Per-Tenant Extensions it will provide a good time frame to fix and test those extensions before actual release is available for SaaS Tenants.

If you are a partner then its time to start testing extensions on Preview Build.

This article will talk about the steps of How to Setup Preview Sandbox?



Step 1 - Check Current Version.

Open Help and Support From Client and Check Version of the Tenant.
As in the below screenshot, you can see that Version is 15.



Step 2 - Open Admin Center.

Click on Setting Gear Icon and select the Admin Center.



Step 3 - Click New in Admin Center, and Provide Following Values for Parameters -

  • Environment Name - Name of Sandbox Environment.
  • Type - Sandbox.
  • Country - As per customer.
  • Select a Version for this environment - Choose 16.0.11209.0(Preview)




Step 4 - Choose yes in Confirmation Message.

Confirmation is - That environment may be updated to a new Preview Version or deleted with or without notice.
** This statement only applies to Preview Sandbox.




Step 5 - Sandbox State will be in Preparing.

As we confirm the confirmation message, Sandbox will start Preparing to setup the environment.



Step 5 - Sandbox Is Ready.

After a while, the State of the new tenant will change to Active and accessible now.



Step 6 - Let's check Version again.

Using Help & Support Menu check version of Sandbox Environment.
Sandbox is updated to Business central 16.0



Sandbox Environment is ready to use for test per-tenant extension and train your team about what's coming new in Next Wave.

How you find the information useful. Please share your feedback as a comment on the article.

#IWishItWasApril

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

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.