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…

Technical code changes in Microsoft Dynamics 365 Business Central 2021 release wave 1 [1]

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:

Source : 1ClickFactory
Read more…

Change multiple Application Area tags with PowerShell

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:

Bron : Dynamics NAV Team Blog
Lees meer…