The Payment Reconciliation Journal feature in Microsoft Dynamics 365 Business Central is a huge time saver for finance professionals. It enables you to automatically (or manually) import banking data files and auto-match to transactions within Business Central. The Payment Reconciliation Journal feature also provides a match confidence to make the process even smoother.
I think I have mentioned before, that I strongly recommend partners to use the extension model and create extensions, which can be published, installed and upgraded much easier then code customizations.
Having said that, I know that there are partners out there for who AL code customizations will be the right stepping stone towards adapting an extension model.
As you already knows from this official Microsoft post, with Dynamics 365 Business Central Wave 2 release Microsoft has splitted the application into two main modules: Base Application (that contains all the ERP business logic) and System Application (that contains all the system layer).
If you are like us at Axians Infoma and can’t make the transition of your on-premises solution from C/AL to AL with a single snap of your fingers, you may want to use hybrid deployments as a first step. This means shipping your standard C/AL solution and publishing dependent extensions on top of that to enable a step-by-step migration to AL.
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: