Skip to main content

MSDYN365BC - Why Customer and Developer Should Choose AL over C/AL?

Hi Readers,

I have received so many comments and email about how to code with New changes.

There are so many confusion and wrong assumptions with these changes that Microsoft is bringing in the product.

Old Way - #MSDNAV  <==> New Way - #MSDYN365BC

In this article, I will like to discuss about Benefits of moving to AL for our Customers and what Developers need to do for these changes. Going forward I will try to cover as much as I know for programmers.

If you are a Customer using NAV / BC (on-Prem) / BC (on-cloud) - 

Every customer either on cloud, on-Prem or in NAV should start requesting partners to do all modification using AL Code.

If all your modifications are in AL, these are short and long-term benefits that you will get - 
  • Applying cumulative update will not be painful and costly. If you wish you can apply them every month.
  • You can install / un-install a modification whenever you want without a developer/consultant help.
  • Your Upgrades will be cheaper (nearly 0 for BC hosted) and quick like never before.
  • Your customization / Modifications will be easy to analyze what they do. Extensions will contain all details like where it impacts the base product and how much it impacts.

If you are a Developer for NAV / BC (on-Prem) / BC (on-cloud) - 

  • Yes, we have a new name but for programmers (developers) or consultants, there are no major changes. Believe it or not, it will be simple if you take these changes with the positive mode or start working toward it.
  • Please don't repeat a mistake like most of us did during the release of NAV 2009 - IGNORE! 
  • We all know how much that ignorance has impacted our work personally as well as for the company and for the customer. Start working on it Today!.
  • The only hard part that we all will have to deal with is - UNLEARN OLD WAY OF DEVELOPMENT / CUSTOMIZATION.

With this being said, let's understand what we do today for customers in NAV. After thinking for a while we only do two things -
  1. Develop New Objects.
  2. Modify Base Objects.
Can you think of anything else?

Microsoft has put so many efforts and added so many features after NAV 2016 (initial release of extension) Extension V1. Currently, we are working on Extension V2 and if I read/heard it correctly there is a V3 that will be releasing soon.

I am starting a series where we will cover both things that we do for our customers - New objects and modifying base objects in VS Code. 

There are still some limitations that Microsoft is working on but don't hold yourself stating "I will learn when its ready!". With this, you will be far behind in the game. 

Learn, Explorer and practice to make your life easier in the future! Stay tuned the first article should be there tomorrow. Be ready with Business Central (on-Prem) installed, VS Code installed on your local machines.

Saurav Dhyani


Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.