Dynamics 365 Business Central: quick reminder for some upcoming changes

October will be the month where Dynamics 365 Business Central 2022 Release Wave 2 (version 21) will be publicly available. But together with this new release wave and the next wave (version 22), partners should be ready for some upcoming changes that I want to remind.

With Dynamics 365 Business Central 2022 Wave 2 (version 21):

  • The Business Central Server Administration tool for configuring the Business Central Server in on-premises installations will be removed in the 2022 release wave 2. From version 21, Powershell and the Business Central Administration Shell will be the one and only administration tool for the server platform.
  • .NET add-ins compiled with .NET Framework won’t work in Business Central 2022 release wave 2. .NET Framework has been superseded by .NET Standard and if you have .NET add-ins for Business Central please check to be .NET Standard compliant. I wrote some posts here and here in the past about this topic, now it’s time to act. UPDATE: this changes will now takes effect from 2023 Wave 1 release.

With Dynamics 365 Business Central 2023 Wave 1 (version 22):

  • Support for the .flf file format for Business Central license files for on-premises deployments will be removed. The new .bclicence file format will be the one and only supported from version 22 and next releases (you will not be able to download or import .flf file in versions >= 22). For the older Business Central versions (<= 21) partners will be able to download a zip file from Partner Center containing .flf and .bclicense files.
  • Support for using an Application Insights instrumentation key to setup telemetry for Business Central environments or apps will be removed. Azure Applications Insights connection string will be the only supported way to ingest telemetries.

I suggest to add a reminder about these topics and act accordingly.

2 Comments

  1. Hi – just to say that transition to .NET standard is not part of October 2022 Wave 2 release. This is now part of 2023 Wave 1. Of course, it is good for people to move to .NET Standard (or move to function apps) – but just to say there is still a bit longer to do this if needed as Microsoft not ready for 2022 Wave 2.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.