Deprecated Features in W1

This article describes the features that have been moved, removed, or replaced in the W1 version of Business Central.

Deprecated features won't be available in future versions of Business Central, and they are deprecated for different kinds of reasons. For example, a feature may no longer be relevant, or something better may have become available. If you use a feature that is listed, either the feature itself or an extension of it, you should look for or develop an alternative.

The next sections give a brief description of the deprecated features, state what happened to the feature, and explain why. The following table gives a few examples of what we mean by moved, removed, or replaced.

State Examples
Moved The capability has been moved from local functionality to W1 because it was no longer specific to one or more country versions. The capability was combined with other related functionality to eliminate redundancy.
Removed The capability will be removed in a coming release.
Replaced Something better has become available, and will be used instead.

This information will change with future releases, and might not include each deprecated feature.

Changes in 2022 release wave 1

.NET add-ins not using .NET Standard (Removal)

The following feature will be Removed with Business Central 2022 release wave 1.

Moved, Removed, or Replaced? Why?
Replaced .NET Framework has been superseded by .NET Standard. .NET add-ins compiled with .NET Framework won't work in Business Central 2022 release wave 1.

Web Service Access Keys (Basic Auth) for Business Central Online

The following feature will be Removed with Business Central 2022 release wave 1.

Moved, Removed, or Replaced? Why?
Removed (for SaaS only) The capability to access web services in Business Central using Web Service Access Key (Basic Auth) is deprecated for SaaS. OAuth2 will be the authentication option for SaaS. OAuth samples are published in the BCTech repo. For on-premises, Web Service Access Key (Basic Auth) will remain an option for the time being. This change has no impact on how Business Central connects to external services.

Permissions defined as data

The following feature will be Removed with Business Central 2022 release wave 1.

Moved, Removed, or Replaced? Why?
Removed With releases of Business Central prior to 2021 release wave 1 (v.18.0), System and Extension permissions and entitlements were defined as data in the application database. This has changed with Business Central v.18.0. With Business Central 2022 release wave 1, the support for defining permissions and entitlements as data in the application database will be removed. For more information, see Entitlements and Permissions Overview.

Changes in 2021 release wave 2

Business Central app for Windows

The Business Central app that's available from the Microsoft Store is no longer supported with Business Central 2021 release wave 2.

Moved, Removed, or Replaced? Why?
Replaced The legacy app for Windows was based on Universal Windows Platform (UWP). In it's place, we offer an app that's based on Progressive Web Application (PWA) technology, which is a more modern technology that provides a better user experience going forward. The legacy app will still be available on the Windows Store for users running Business Central 2021 release wave 1 or earlier.

Removal of the Business Central Server Administration tool (Warning)

The following feature will be Removed in a later release.

Moved, Removed, or Replaced? Why?
Removed The Business Central Server Administration tool for configuring the Business Central Server in on-premises installations will be removed in a later release. Please transition to using the provided Powershell cmdlets in the Business Central Administration Shell instead.

StartSession calls in upgrade/install context will fail

The following feature will be Removed with Business Central 2021 release wave 2.

Moved, Removed, or Replaced? Why?
Removed A new session created with AL StartSession has no link to the session that created it. This implementation can cause problems, for example, in cases where the creating session is an upgrade codeunit. If an error occurs later in the process, which requires a rollback, the server can't roll back any transactions done in the session created by the AL StartSession. This condition can leave data in the system in a bad state. Starting with Business Central 2021 release wave 2, any StartSession call in upgrade/install context will fail immediately.

Standard APIs, Beta version

The following feature will be Removed with Business Central 2021 release wave 2.

Moved, Removed, or Replaced? Why?
Removed Beta version of the standard APIs will be removed by 2021 release wave 2. At this point, Beta APIs won't be available in new releases of Business Central. There are many improvements to v1.0 and v2.0 of the standard APIs. Improvements include more APIs, better performance and improved OData capabilities. It's recommended that integrations move to v2.0 of the standard APIs.

Automation APIs, Beta version

The following feature will be Removed with Business Central 2021 release wave 2.

Moved, Removed, or Replaced? Why?
Removed Beta version of the Automation APIs will be removed by 2021 release wave 2. At this point, Automation Beta APIs won't be available in new releases of Business Central. It's recommended that integrations move to v2.0 of the Automation APIs.

Client secret authentication in integrations between Microsoft-hosted Business Central online and Microsoft Dataverse

The following feature will be Removed with Business Central 2021 release wave 2.

Moved, Removed, or Replaced? Why?
Removed The ability to connect Business Central with Dataverse using the client secret Service-to-Service authentication will be removed for online tenants hosted by Microsoft in March, 2022. To further strengthen security, we introduced the ability to use certificate-based authentication in Business Central 2021 release wave 1 (version 18 and later). Existing users can easily switch to certificate-based authentication. For more information, see Upgrade Connections from Business Central Online to Use Certificate-Based Authentication. On-premises customers, and online tenants that are hosted by ISVs, can continue using client secret authentication for their connections to Dataverse.

Legacy Outlook add-in for synchronizing data

The legacy Outlook add-in for synchronizing data, such as to-dos, contacts, and tasks, between Business Central and Outlook will be Removed with Business Central 2021 release wave 2.

Moved, Removed, or Replaced? Why?
Removed This add-in used Business Central web services based on outdated technology.

Note

The feature is separate from and has no affect on the Business Centraladd-in for Outlook, which is described at Using Business Central as your Business Inbox in Outlook.

Changes in 2021 release wave 1

.NET add-ins not using .NET Standard (Warning)

In Business Central 2021 release wave 1, a warning shows if you include .NET add-ins that are compiled with .NET Framework and not with .NET Standard. The capability of using .NET add-ins compiled with .NET Framework will be removed in a later release.

Moved, Removed, or Replaced? Why?
Replaced .NET Framework has been superseded by .NET Standard. .NET add-ins compiled with .NET Framework is deprecated as of Business Central 2021 release wave 1, but the feature won't be removed in this release. It's recommended that .NET add-ins are migrated to .NET Standard as soon as possible.

Expose UI pages as SOAP endpoints (Warning)

In Business Central 2021 release wave 1, a warning shows if you expose UI pages as SOAP endpoints. The capability of exposing UI pages as SOAP endpoints will be removed in a later release.

Moved, Removed, or Replaced? Why?
Replaced SOAP has been superseded by OData V4. SOAP endpoints are deprecated as of Business Central 2021 release wave 1, but the feature won't be removed in this release. It's recommended that integrations are migrated to OData V4 as soon as possible.

OData V3

The following feature is Removed with Business Central 2021 release wave 1.

Moved, Removed, or Replaced? Why?
Removed OData V3 has been superseded by OData v4. OData V3 is deprecated, and is removed as of Business Central 2021 release wave 1. It's recommended that integrations are migrated to OData v4 as soon as possible.

The Help Server component

The following component is Removed with Business Central 2021 release wave 1.

Moved, Removed, or Replaced? Why?
Removed In 2021 release wave 1, the Help Server component is removed from the product media for deployment on-premises. If a customer is on a version between Dynamics NAV 2016 and Business Central 2020 release wave 2 on-premises, and they rely on Help Server to provide access to Help, then nothing changes. When they upgrade to Business Central 2021 release wave 1, they must host their custom Help on another type of website. We recommend that new solutions do not rely on the Help Server component due to the deprecation. The custom help toolkit can help deploy content to any website, for example.

What does this mean?

We have simplified the story for how to deploy Help for a customer-specific solution of Business Central, and for deploying Help for an AppSource app. No matter what your solution is, deploy your solution-specific or customized Help to any website that you prefer. Out of the box, Business Central uses the Docs.microsoft.com site for the Learn more-links and contextual Help. Each customer and each partner can override this with their own Help. It's now the same for Business Central online and on-premises, so any investment on-premises carries forward if you migrate to Business Central online.

Deprecated Features in 2020 release wave 1

The following feature was marked as obsolete:pending in 2020 release wave 1.

Best Price Calculations

When you have recorded special prices and line discounts for sales and purchases, Business Central ensures that your profit on item trade is always optimal by automatically calculating the best price on sales and purchase documents and on job and item journal lines.

Moved, Removed, or Replaced? Why?
Replaced The functionality is replaced with new calculations that you can extend to include additional sources or calculation methods. The current capabilities will be available, and can be used in parallel with the new, until 2021 release wave 1. For more information, see Extending Best Price Calculations.

Deprecated Features in 2019 release wave 2

The following sections describe the features that were deprecated in 2019 release wave 2.

The Bank Data Conversion Service

You can use the bank data conversion service from AMC to convert bank data from an XML file that you export from Business Central into a format that your bank can accept.

Moved, Removed, or Replaced? Why?
Moved The functionality has been moved to an extension. It now ships as the AMC Banking 365 Fundamentals extension, which can convert bank data to formats that are used by more than 600 banks worldwide. For more information, see Using the AMC Banking 365 Fundamentals extension.

The Windows Client

You can use Business Central in the Windows client that is installed on your computer.

Moved, Removed, or Replaced? Why?
Removed Business Central continues to evolve the modern client experiences where users work with Business Central in the browser, Windows 10 desktop app, or mobile apps on Android and iOS. The legacy Dynamics NAV Windows client is no longer available for deployment. Instead, users can switch to the modern experience in the browser, the Android/iOS mobile apps, or the Windows 10 desktop app (available through the respective stores).

Reports 204-207

You can generate external-facing documents, such as sales invoices and order confirmations, that you send to customers as PDF files.

The reports in the 204-207 range are replaced by the following updated reports in the 1304 to 1307 range:

  • 204, Sales-Quote -> 1304, Standard Sales-Quote
  • 205, Order-Confirmation -> 1305, Standard Sales-Order Conf.
  • 206, Sales-Invoice -> 1306, Standard Sales-Invoice
  • 207, Credit-Memo -> 1307, Standard Sales-Credit Memo

Note

The No. of Copies field is removed from the new reports because of performance reasons and because selection of the quantity to print works differently on modern printers. To print a report more than once, users can list the same report multiple times on the Report Selection page for the document type in question.

Moved, Removed, or Replaced? Why?
Replaced The reports in the 204-207 range are replaced by the reports in the 1304 to 1307 range. To avoid duplicated features, the reports in the 204-207 range will be removed.

User Personalizations and Profile Configurations

You can personalize pages and configure profiles by adding or removing fields, and Business Central will save your changes.

Moved, Removed, or Replaced? Why?
Replaced The shift to AL caused the legacy personalization and profile configuration features to become outdated, so we have introduced new tooling. In this release, existing personalizations and configurations are discarded, and you must use the new tools to recreate them. Your new changes will be kept in future releases.

Excel COM Add-In

You can export data to an Excel workbook.

Moved, Removed, or Replaced? Why?
Removed The Excel COM add-in was installed along with the Windows client. Now that the Windows Client is no longer available, neither is the add-in. To export data to Excel, use the Edit in Excel action.

Printing Programmatically

You can print documents such as invoices automatically, without prompting the user or without the user choosing to do so.

Moved, Removed, or Replaced? Why?
Removed This feature was tied to the Windows Client, which is no longer available.

Objects that have been marked as obsolete

Part of deprecating features is marking the objects that comprise them as "obsolete." Before we deprecate an object, we tag it as "obsolete:pending" to alert our partners of it's deprecation. The object will have the tag for one year before we remove it from Business Central.

Breaking Changes

When we move, remove, or replace an object, breaking changes can result in other apps or extensions that use the object. To help our partners identify and resolve breaking changes, we have created a Breaking Changes document that lists known issues and suggestions for what to do about them.

Features that are available only in the online version

Some features are available only under very specific circumstances, or not at all intended for use in on-premises versions of Business Central. For a list and descriptions of those features, see Features not implemented in on-premises deployments.

See Also

AlAppExtensions repository
Best Practices for Deprecation of Code in the Base App
Microsoft Timeline for Deprecating Code in Business Central