Skip to main content

#msdyn365 End of the Beginning.


Hi Readers,

If you haven't noticed End of the Beginning already started 05 months ago.

In this article we will discuss about what does that mean and how does that impact #msdyn365bc customers.

#msdyn365bc, #endofbeginning

If you don't remember Microsoft Released Modern Lifecycle Policy. You can read more about it here.

With this policy in effect from Business Central 15 (a.k.a msdyn365bc 2019 wave 2), every version will be in mainstream support for only 1.5 Year.

As soon as Business Central 18 was released, Business Central 15 was out of mainstream support.

Customer cannot purchase business central 15 license and if a customer was upgraded to Business Central 15 then they should upgrade to Business central 18.

What was Unique about Business Central 15 (msdyn365bc 2019 wave 2?

Business Central 15, you will be known as the stepping stone in this new world were we are today.

  • BC15 was the beginning of New Era.
  • BC15 was first version where there was no C/AL.
  • BC15 was first version with AL only.

Upgrade Again ? What Do you mean?

  • In Modern world, upgrades are not same as in Legacy (C/AL) world.
  • Partners will be able to upgrade you easily. With every mod as extension partners only have to work on any obsolete features or deprecated code.
  • What we have understand being part of upgrade team is, Upgrades are super easy in Modern environment.
  • As soon as every time a new version released one version will be discontinued going forward.
  • Every Six Month, as New version is released a old version is out of Mainstream support.  

Why Upgrades are Easier?

  • Upgrades are easier and there are proofs for it. 
  • Customers who are using Business Central Online are getting upgraded Every month. 
  • Cumulative Upgrades are happening automatically in BC SaaS Every Month. 
  • With all code in Extensions, its gets simple enough to upgrades customers.
  • Partners can practically automate on-Prem upgrades as Microsoft is doing them in BC Online.

Upgrades will not be simple for?

  • If your partner instead of Eventing your customization, modified base app from Microsoft.
  • If you are using an ISV who is customizing Base App from Microsoft.

Summary

In Modern world, Upgrades are simple as it happens with all other applications / devices.

Think about Windows Update, Office Updates or your mobile device updates. Business Central is also added in that list.

Automatic Upgrades are future with this modern world.

Please add your views in comments to this article.

Regards,
Saurav Dhyani

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

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.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.