Skip to main content

How Business Central Modern Client Reverse Compatibility With NAV Can Help You Improve Your Work.

Introduction:

Today, I was playing around with Business Central Modern Client (Windows App).
Out of curiosity I was trying to login to one of my NAV 2017 through SSO.

Pre-requisites:

Microsoft Dynamics NAV with SSO configured
Microsoft Dynamics Business Central

Demonstration:

1. Business Central App - Main Page:

Business Central Modern Client - Main Page
Clicking on locally hosted service and putting in the credentials configured for NAV 2017 SSO, we get.
Business Central trying to Log In into NAV
Still skeptical when Business Central login into NAV.

2. Business Central App - Reverse compatible with NAV 2017:

NAV in Business Central Modern App

Well well well...
Look whose here.
NAV disguised as  Dynamics 365 for Financials.

I think we all agree that Business Central Modern Client is a WebApp version of Busines Central Online. Basically just like browser in an App.
The difference is that it can connect to NAV as it is just like a browser.

3. Does Business Central Modern Client follow DynamicsNAV protocol?:
Well, it simply does not.
It would be amazing  if it did, as it would mean that we could deal with running tables directly rather than changing the data in it using configuration package.

Conclusion:

I was surprised to see this for a couple of reasons one of which majorly included the difference in system architecture for NAV and Business Central and difference in Database after the upgrades.
It is really nice to see Business Central Modern App compatible with NAV and it kinda restores my faith that no matter whatever happens, Business Central is still NAV which most of the users will agree that they are still comfortable with.

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.