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

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.