Skip to main content

Business Central Admin Center Upgrade with Business Central Wave 2 2020

Introduction:

In this blog, I'm going to demonstrate the newly available Business Central Admin Center coming up in October for the 2020 Release Wave 2 

Pre-requisites:

  • Business Central Admin Center

Demonstration:

1. Changes to Business Central Admin Center:
After you login in Business Central Admin Center, you will observe a couple of changes in the Admin Center on the Main Screen directly. The changes are missing actions, additionals sections.

2. Changes on Environment Card Page:
After selecting the environments, you will notice key things such as renaming the environment.

3. Update Settings in Business Central Environment:
When you click Update Setting, you have the ability to schedule Update Windows and Date.


4. Renaming Business Central Environment:
While this was an easy one, the best one so far is the 'Renaming' feature 


5. Delete Action feature moved to Environment Card: 
There is another one where the actions on the Environments List Page is moved to the card page.


6. Enabling Application Insight Key:
Using Application Insight Key to monitor Business Central Environment and creating reporting on basis of the data gathered.

7. Checking the status of Reported Production Outages:
Using the Reported Production Outages, you can check all Reported Issues and track it. Through the CSP Portal.


8. Checking the Database Capacity:
Business Central v17 enables you to check the Database Capacity for the Environments. Although its not possible to show it with BC v16.


From here, you can also check the size of each of the tables. This will take you to page 8700 - Table Information.

Conclusion:
Well, I was surprised to see this feature coming up prior to release.
The best feature I really wanted was Renaming Environment, Capacity, and Report Outage.

I hope this helps 



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