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

TIP: Working with changing Field DataTypes and Deleting fields in Business Central

Introduction:
Imagine a scenario where as per the requirements provided by your clients, you have set up the Database structure in NAV/Business Central.
Then comes a requirement in Phase 2 which completely redefines the database structure which was provided by you and you need to delete a few fields in a table and move it to another table.

Pre-requisites:
Microsoft Dynamics NAV
Microsoft Dynamics Business Central

Books & References:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-property

Solution:
1. In Microsoft Dynamics NAV, there was a flexibility to delete fields, tables, and keys and using  Force-Sync, you can directly delete the field, table, and keys from SQL Database.


2. Whereas in Microsoft Dynamics Business Central, you cannot delete the fields, keys, and tables.
In order to deploy this deleted change, you need to mention this field, table, and keys with Obsolete State Removed.


After you mention the field as…

How to actually use Profile Objects in Business Central

To 'Whomsoever This May Concern',
When I was working on a Production Deployment for one of my clients, I noticed that I could not create a Profile in Business Central Production Tenant. I was able to create new Profile in Sandbox.


Then I tried using configuration Package and modify the contents of 2000000178 Profile Table and as always configuration package blocked it.



There was no way of dealing with this other thancontacting Microsoft Support and this is the answer I get from a Support Engineer

I was on the verge to give my clients a link pointing to a specific page i.e https://businesscentral.dynamics.com/?page=50150

After being a little creative, I figured out that developing profile objects might help.

And this resolved this issue for me.




Permission Issues on Posting after deploying Extension in Business Central Production Tenant

Introduction:
Issues when you deploy your app in Business Central Production VS Business Central Sandbox. Let us what are the implications of the statement.
In my last blog () I have already pointed out the difference in Profile as to how can create new Profile in Business Central Sandbox but the same is not possible in Business Central Production.
Pre-requisite:
Microsoft Dynamics Business Central (SaaS)
Demonstration: 1. I was working with General Journals after deploying the App in Production Environment. Suddenly during posting I go this error.


2. To Verify this issue is not of Permission Set, I gave the User SUPER Permission and tried again.

I got the same error despite giving SUPER Permission. Again the same the error, so I checked the Effective Permissions.

I noticed that Table G/L Entry has an Indirect Permission. I replicated the same Production in Sandbox. But I didn’t find any issue like this.

3. Moreover, I noticed that when I uninstall the App, the Production works perfectly and …