There’s a lot of talk right now about Microsoft Dynamics 365 Business Central version 14. Microsoft recently extended the end date for buying new version 14 licenses (Written in August 2020), this thing cannot die?

So what’s so about special about version 14?

Version 14 was the last version that supports C/Side. C/Side is the classic development environment, first introduced in 1995/1996. In version 15 the base application became an app or an extension just like all the new apps we’re creating.

Version 14 also supports extensions, in a version that usable for app development (yes, NAV2018 introduced extension, but that was a limited version, missing many essential events).

So version 14 is great?

Yes, version 14 is awesome, and a necessary step when converting from C/Side an extension based solution.

The path is simple, upgrade your C/Side solution to version 14, use Uplifting to move the data to your new extension and you’re ready to either go to the cloud or upgrade to the latest on-premises version.

Microsoft’s Cloud Migration tool supports version 14, so as soon as you’re on 14 without any C/Side customization, you’re ready for the cloud.

So version 14 is bad?

No, but if your solution is C/Side based, and that’s the reason you’re “stuck” with version 14, then yes, that’s quite bad.

ISV and partners have had since late 2017 (Release of NAV2018, aka version 11) to work on their solution and transition to an extension. We have now passed the start of 2021 and version 18 is due in less than 2 months.

But the ISV solution I want is still C/Side?

Buying and installing a new version 14 Business Central, because an ISV solution is still based on C/Side, seems like a terrible business decision, You’re simply installing technical debt.

The vendors have had almost 4 years to get their solutions to extensions, the community has supplied with tons of tools and shared their experience about this. If an ISV in 2020 is still clinging to C/Side, I’ll suggest finding another solution that is more future-proof from a vendor that’s willing to invest in their products.

I’m still installing version 14, now what?

Let me list some of your issues: (apart from missing the added features in new versions)

Let mw know on Twitter @eHougaard if I missed something on this list?

All-in-all, you’re installing technical debt and you should walk into that with open eyes and an open wallet.

(I also know of ISV solutions that are stuck on version 13, even worse).

5 Responses

  1. I feel you may have missed the issue here. It has nothing to do with C/SIDE, I am sure customers don’t really care about what editor is used to write the code. The core reason for upgrading to 14 is to be on the latest version that works with the Windows client. There are many customers that are not able to work with the web client.

    1. OK, I’ll bite ๐Ÿ™‚

      So it’s all about the Windows client, because you’re using .NET based control addins? (The only thing that the webclient cannot do?)

      And if it’s all about the client, then you’re NOT using C/Side for development, everything is done as an extension and there are NO C/Side modified objects?

  2. In addition, there are tens of thousands of Navision clients out there for whom moving to the web browser, is not an upgrade, it is a completely new ERP implementation. For many of those if they can’t move to 14 they will simply shop around for a new product.

    Taking away the stepping stone from Navision to BC would alienate a lot of customers.

    1. I respectfully disagree, I think many partners have pushed their view on clients. All the NAV customers I have shown the client to, like it, and IT managers love it.

      This is NOT a “tens of thousands” issue….

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.