Skip to main content

Changes to Business Central Admin Center in 2019 Wave 2 Release

Introduction:

In this blog, I plan to cover the changes in Business Central Admin Center in 2019 Wave 2 Release.

Prerequisites:

Microsoft Dynamics Business Central

Demonstration:

Changes in Business Central Admin Center are as follows

1. Changes in Action Button and addition of Refresh Button in Environments section:
List of Environments and Actions


2. Addition of Action Buttons Environment Card (Details) Page:
New Additions in Action are Report Production Outage and Manage Support Contact
Environment Details and Actions

You can create a Support Ticket for the Tenant, Report Outages in Production and also Delete the Production as multiple Production Environments are supported.

3. Creation of New Environment:

  • Creation of New Environment either multiple Production and Sandbox.
  • Can select appropriate Country Region for the Environment.
  • Can even select version including version 15.03650.0 for Production and above versions such as 15.0.36135.0 (Preview) for Sandbox

Creation of Environment


4. Report Production Outage (Only in Production):
Report Production Outage Enabled in Production
Report Production Outage Disabled in Production
Reported Production Outages - Filter by Days 


5. Manage Support Contact:
Manage Support Contact is In Development. You can refer to Release Plan to know more.
Manage Support Contact


Limitations of Admin Center:
1. Can provision only single environment at a given time.

Conclusion:

Overall the changes I liked in terms of Productivity are Refresh Button Environments section, Selection of Country for the Tenant, Report Outages and ability to Support Case Ticket.

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe