For example, in Dynamics 365 Business Central version 14, we witnessed the elimination of Codeunit 1, the methods of which were spread among multiple other Codeunits. It was not a big change as it resulted in only a few hours of adjustment work in order to adapt to the change. But overall, it required the additional attention and effort of most Dynamics Partners.
The bigger change in Dynamics 365 Business Central version 14 was the field expansion. At the beginning, it didn’t seem significant as most of the description fields had already been expanded. But as customers started to enter the longer names it became apparent that their solutions were dependent on standard applications which were not adjusted to support the new field length. This change didn’t break the solutions but resulted in Run Time Errors for most of the Customers.
Further on, in Dynamics 365 Business Central version 15, the C/AL and RTC Client were discontinued. This was a significant change. On top of that, the System App was introduced. And altogether there was a lot of restructuring and refactoring happening in the core functions of Business Central, such as the total reimplementation of BLOB handling.
There were fewer changes in Dynamics 365 Business Central version 16. One of them was the Proxy App. Initially, the Proxy App was introduced in one of the minor releases of Business Central version 15 but required the dependent Apps to be changed and recompiled. In addition, in Business Central version 16, most of the standard Option fields were changed to Enums. Even though this was not a Breaking Change, in the Compiler we now get a warning that assigning an Option value to Enum data type will be discontinued in a future Business Central release. This gives us some time to adapt and encourages everyone to get ready for a change that’s coming in the future.
The upcoming Dynamics 365 Business Central version 17 update will be rolled out from October 2020 to March 2021. It is predicted to include “With” statement discontinuation and the change of pricing functionality that Partners will have to reimplement with Interfaces. Therefore, even though the old methods will be supported for a while, eventually the changes will make the current implementations obsolete compelling all Dynamics Partners to adapt.
In future Dynamics 365 Business Central releases, plans are being made to implement localizations as Extensions. It might take some time as it requires the collection of all the redundant functionality implemented by different localizations, then moving it to the Base App and then making the Base App extensible enough to support the requirements of localizations. Given this, I anticipate a lot of restructuring in the future. Additionally, there is a plan to split the Base App into multiple modules as Apps so that the separate modules can be replaced by the Dynamics Partner solutions. This also requires a lot of refactoring and may require a lot of restructuring changes in the future.
As we look back on the Dynamics 365 Business Central evolution over the recent years, it becomes obvious that Business Central SaaS upgrades are required. The good news is that they will be simpler and lighter. The bad news is that they will be more frequent and mandatory.