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:
Before you convert an existing Dynamics NAV solution to an extension written in AL, the ApplicationArea property must be set on all your custom controls. Otherwise, they will not be visible.
Setting the ApplicationArea property one by one is a tedious task that can be partially automated with the following PowerShell scripts: