Skip to main content

Changes to Admin Center for v15.4, v16 in Microsoft Dynamics 365 Business Central Online(NAVISION ERP)

Introduction:

With Business Central already upgraded to v15.4, and soon about to upgrade to v16 after 1st April 2020, there are very useful features being added to Business Central Administration
I'm super excited to blog about these. Let us check them out.
I think its finally time to say "Now we are talking!"

Pre-requisites:

  • Microsoft Dynamics Business Central Online
  • Access to Microsoft Dynamics Business Central Admin Centre

Demonstration:

Change #1: Layout of List of Environments
A clean and a user friendly layout change can be observed in the List of Environments.
You can see fields such Available Update Version, Scheduled Update Date
List of Environments
List of Environments selection

Change #2: Environment Details
New Actions -

  • Manage Apps: In this you can see what all apps are installed in your Business Central Environments
  • Manage Sessions: In this you can see all the sessions running for your Business Central Environments
  • Application Insights Key: Use to log all your Telemetry to Azure Applications


New Fields -

  • Available Update Version: In this you can check which is the Available Update Version
  • Update will start on or after: 
  • Update Scheduling Available(?): After clicking on the '?' it redirects you to https://aka.ms/bcupdates
  • Update Roll-out State(?): After clicking on the '?' it redirects you to https://aka.ms/bcupdates

Environment Details

Change 3#: New Support Request Action
This action has been previously in development is now complete. When you click on this it takes you to Power Platform Admin Center for your cases and where you can also raise a paid case ticket.
New Support Request


Change 4#: Manage Apps
Here you can see the Apps installed in your Environment. Here you will not be able to find your customized app but only the ones installed from Market Place or default apps.
Manage Apps

Change 5#: Manage Sessions
Here, you should be able to see all the logged in sessions. You can manually kill each session. This is one of the best feature I feel as many users would get stuck if there was any discrepancy in logging due to multiple sessions. So we had to get them logged out through whole Dynamics 365 for this session to be closed.

Manage Sessions


Cancelling a session
 
Cancelling a session

Change 6#: Application Insight Key

 Here, you can log your telemetry to Azure and inspect to make analysis. Refer below
https://demiliani.com/2019/11/18/dynamics-365-business-central-handling-telemetry-with-azure-application-insights/

Conclusion:

For now, I think it is a good improvement and I'm really liking as to how to product is getting matured and where the things are headed.

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 update your Business Central to Latest CU

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i