Monday, March 2, 2020

MSDYN365BC 2019 Wave 2 - Upgrading an Modified C/AL Database.

Hi Readers,

In this article, we will discuss Upgrading a database to Business Central Wave 2 from Business Central Spring 2019 Release (14.x).

This all is for a Business Central Spring Database that does include C/AL Code Customization.

I didn't want to write this article but as multiple people requested it I am writing it but I don't support this approach.


#MSDYN365BC #BC2019Wave2

Point to Remember -
  1. This is a multiple article post.
  2. This article does not follow what Microsoft suggests the way do it with your own risk.
  3. There is a reason why I liked this approach as it follows the correct Upgrade Process.
  4. The scenario created for this article is not the scenario that will require this approach.
  5. ** With this article, I am not suggesting that you should ever do this but if you have to then I suggest this way.

Table of Index - 

  1. Upgrading a Modified C/AL Database - Part 1.
  2. Upgrading a Modified C/AL Database - Part 2.
  3. Upgrading a Modified C/AL Database - Part 3.
  4. Upgrading a Modified C/AL Database - Part 4.
  5. Upgrading a Modified C/AL Database - Part 5.
With this upgrade, we will merge all C/AL base customization from Business Central 14 to Business Central 15 (Wave 2) Base App. Then we will use that custom Base App during Upgrade.

Questions (Maybe I can answer here If any additional please add them as a comment to this article).

Question 1 - What is Microsoft Suggested Way of Upgrading a Modified Database?

Microsoft suggests using Technical Upgrade from BC14 to BC15 as shown below.

Microsoft Way - 




Question 2 - Why are we not using Microsoft Approach?

Microsoft Approach as discussed in this MSDN Post is about Technical Upgrade from BC 14 to BC 15, Which is not an actual upgrade. I love to use the same Executables and Same Codebase which means that with Microsoft Way I will not do what I feel is best for my customer.

My Way - 




Question 3 - Why are you not suggesting using this approach?

The whole idea why Microsoft switched to use Extension Model is to reduce the cost of upgrades. If we don't use the Extension Model then you are not doing justice to your customer. This also means that you are actually promoting your customer to Switch from Dynamics NAV/Business Central to other ERP Products.

You should do what is best for the customer and try to save their Future Cost with Upgrades. At the said time I believe that its partner who is responsible to keep customer Upgraded to Latest and greatest version of Product.

Second Very Important Reason - Microsoft will disallow customizing Base Microsoft AL Application in the Future. There is no defined date from Microsoft about this but Microsoft confirmed that it will be disabled in the future.

If you wait when Microsoft blocks it, the cost of Upgrading will be huge when you plan removes customs from base AL.

Question 4 - What should I setup to follow these articles?

Install Following Versions -
  1. Business Central 14 (Cumulative Update 08).
  2. Business Central 15 (Cumulative Update 03).
** If you have other versions then install products based on Compatibility Matrix. Read Here for Compatilabe versions before upgrading.

Stay tuned for more.

Hope you find it useful.

Let me know your views as a comment on this article.

Regards,
Saurav Dhyani
https://saurav-nav.blogspot.com

No comments:

Post a Comment