In Business Central you can set up Change Log Entries to log insert/modify/delete events for all the fields in all the tables.
But can you do this automatically in the code without even setting up the Change Log Entry? It is quite easy actually.
In Business Central you can set up Change Log Entries to log insert/modify/delete events for all the fields in all the tables.
But can you do this automatically in the code without even setting up the Change Log Entry? It is quite easy actually.
Flowfields play a central role in Business Central, and a common development request is to react when a flowfield changes, but how do you actually do that? Check out the video:
As you probably have noticed, once you upgrade your extension from previous Business Central versions to BC20, their various errors should appear that need to be refactored. So in this article, I will present the most common cases and how to rework them when you upgrade the extension to the Business Central 20 OnPrem version.
I’ve received a request from a partner asking why adding a return value to a procedure in a Dynamics 365 Business Central extension that previously had no return value is considered a breaking change during AppSource validation.
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:
A simple, dependency-free JavaScript add-in that displays a company dropdown on the top titlebar.