Business Central 21, Business Central 22 Breaking changes

Upgrading software to newer versions often involves a series of changes and adjustments to ensure seamless compatibility and improved functionality. In the context of Business Central, upgrading from previous versions to BC21, BC22 may require developers to address breaking changes and refactor their extensions.

Source : Simplanova
Read more…

How to automatically log changes to a field without setting up Change Log Entries in Business Central

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.

Source : integrated.ee
Read more…

Guidelines for Partners: Business Central 20 OnPrem breaking changes

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.

Source : Simplanova
Read more…

Dynamics 365 Business Central: breaking change when adding a return value to a procedure

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.

Source : Stefano Demiliani
Read more…