This is the second part of a two-part blog series on technical code changes in Microsoft Dynamics 365 Business Central 2021 release wave 1. In Part 1 of the blog series, the pending and removed ObsoleteState warnings were covered.
After the in-depth review of the latest code changes, I created a two-part blog series, in which I compare Dynamics 365 Business Central versions 18, 17, 16 and 15, to see the differences between the versions and to understand the necessary adjustments that need to be made to make Microsoft Dynamics 365 Business Central solutions code compatible with new and future releases.
In the first part of this two-part blog series, I focus on pending and removed ObsoleteState functionality:
In the training I’ve done to some partners last week, when talking about performances I shared an example of an extension with 3 features that I think are not so well known but that have a significant impact on how your code performs, expecially on a SaaS environment. That extension used the following features:
-Partial record loading
A question I get a lot – especially from people that come from C/AL, and only take their first steps into AL – is: How do I get to Microsoft’s source code of the BaseApp (and other)?
Well, there are multiple ways, really. You can download symbols, and unpack the symbols. You can download the DVD and get to the code on the DVD, or…