A common challenge in many business management applications is avoiding unwanted changes in data. It could be anything from an incorrect customer name to an incorrect posting to the general ledger. In this blog we will summarize how to Monitor Changes in Dynamics 365 Business Central 2020 release wave 2. There are currently three ways.
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
Since the base application is no longer available through C/Side in Dynamics 365 Business Central Release Wave 2, we need an alternative way of searching for objects and debugging.
That means that we firstly need to find the base application.
In this article, we will discuss Upgrading a database to Business Central Wave 2 from Business Central Spring 2019 Release (14.x).
This all is for a Business Central Spring Database that does not include any C/AL Code Customization. The database can only include Third Party and Custom Extensions.