Deprecated Features in the Base App

Article
12/11/2024

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.

Note

Azure Active Directory is now Microsoft Entra ID. Learn more

Changes in 2026 release wave 1

The following features will be removed in 2026 release wave 1.

API (v1.0) for Business Central (removed)

Moved, Removed, or Replaced?	Why?
Replaced	With Business Central you can create Connect apps. Connect apps establish a point-to-point connection between Business Central and a 3rd party solution or service using the standard REST API to interchange data. In 2020 release wave 2 we introduced a new improved API where all complex properties are replaced with first-level properties or navigation properties. This change significantly improves API performance, as complex fields were previously calculated at runtime. In API v2.0, all multipart keys and non-GUID keys are replaced with unique GUID keys, and entities can be retrieved using the SystemId, which is immutable, platform-enforced, and indexed. This change improves auditing and API reading performance. The API (v1.0) will be removed in 2026 release wave 1. The API v2.0 contains all the functionality from API v1.0, so migration should be possible. If this isn't the case, reach out to us via https://github.com/microsoft/ALAppExtensions. To learn about the replacement feature, go to Transitioning from API v1.0 to API v2.0.

Moved, Removed, or Replaced?

Why?

Replaced

With Business Central you can create Connect apps. Connect apps establish a point-to-point connection between Business Central and a 3rd party solution or service using the standard REST API to interchange data.

In 2020 release wave 2 we introduced a new improved API where all complex properties are replaced with first-level properties or navigation properties. This change significantly improves API performance, as complex fields were previously calculated at runtime. In API v2.0, all multipart keys and non-GUID keys are replaced with unique GUID keys, and entities can be retrieved using the SystemId, which is immutable, platform-enforced, and indexed. This change improves auditing and API reading performance.

The API (v1.0) will be removed in 2026 release wave 1.

The API v2.0 contains all the functionality from API v1.0, so migration should be possible. If this isn't the case, reach out to us via https://github.com/microsoft/ALAppExtensions.

To learn about the replacement feature, go to Transitioning from API v1.0 to API v2.0.

Legacy Power BI apps on AppSource

Moved, Removed, or Replaced?	Why?
Replaced	While useful to show the Power BI embed capabilities in Business Central, the legacy Power BI apps on AppSource have now been superseeded by the 7 Power BI apps for finance, sales, purchasing, inventory, projects, and manufacturing that were released in the 25.1 version. To learn about the replacement features, go to aka.ms/bcAnalytics.

Changes in 2025 release wave 1

The following features are marked as obsolete:pending in 2025 release wave 1.

Excel reports on the Business Manager and Accountant role centres

Moved, Removed, or Replaced?	Why?
Replaced	While useful to some organizations, the Balance Sheet, Income Statement, Statement of Cash Flow, Statement of Retained Earnings, Sales Taxes Collected, Customer Statements, Aged Accounts Payable, and Aged Accounts Receivable Excel reports that are currently available on the Business Manager and Accountant Role Centres are hard to change. To change them requires technical skills in AL and VBA programming. We've enhanced analytics capabilities in finance in each release wave over the last three years. For example, we've added data analysis capabilities on ledger tables, reports with Excel layouts that allow users to change the layout as they see fit, and Power BI reports for finance. To learn about the replacement features, go to aka.ms/bcFinanceAnalytics.

Moved, Removed, or Replaced?

Why?

Replaced

While useful to some organizations, the Balance Sheet, Income Statement, Statement of Cash Flow, Statement of Retained Earnings, Sales Taxes Collected, Customer Statements, Aged Accounts Payable, and Aged Accounts Receivable Excel reports that are currently available on the Business Manager and Accountant Role Centres are hard to change. To change them requires technical skills in AL and VBA programming. We've enhanced analytics capabilities in finance in each release wave over the last three years. For example, we've added data analysis capabilities on ledger tables, reports with Excel layouts that allow users to change the layout as they see fit, and Power BI reports for finance.

To learn about the replacement features, go to aka.ms/bcFinanceAnalytics.

Legacy Power BI apps on AppSource

Moved, Removed, or Replaced?	Why?
Replaced	While useful to show the Power BI embed capabilities in BC, the legacy Power BI apps on AppSource have now been superseeded by the 7 Power BI apps for finance, sales, purchasing, inventory, projects, and manufacturing that were released in the 25.1 version. To learn about the replacement features, go to aka.ms/bcAnalytics.

Changes in 2024 release wave 2

The following features are marked as obsolete:pending in 2024 release wave 2.

Configuration packages for setup and evaluation data

Important

We will remove this feature in update 25.2.

Moved, Removed, or Replaced?	Why?
Replaced	We've changed the way we prepare databases for new evaluation and production companies. Instead of using configuration packages to add demo and setup data, you now use the Contoso Coffee demo data app. We shipped the Contoso Coffee demo data app in an earlier release to cover gaps in our demo and setup data, such as Manufacturing, Service, and Warehouse. Because the app is easy to use and now provides the comprehensive setup and demo data that was previously available in configuration packages, we're removing the configuration packages. To do that, we had to change how the Create New Company assisted setup guide initializes new companies with data. Our changes might affect your extensions. For details about what we removed, explore the Object and What's removed listings.
Removed	Enum 9120 "Company Data Type (Internal)" Enum 9121 "Company Data Type (Sandbox)" Enum 9122 "Company Data Type (Production)" Codeunit 1799 "Import Config. Package File" Codeunit 1800 "Assisted Company Setup": * procedure WaitForPackageImportToComplete * procedure FillCompanyData * procedure ExistsConfigurationPackageFile * procedure FindConfigurationPackageFile * procedure SetUpNewCompany * event OnAfterAssistedCompanySetupStatusEnabled * event OnBeforeScheduleTask Codeunit 1805 "Import Config. Package Files" Table 1802 "Assisted Company Setup Status": * field Import Failed * field Package Imported * procedure SetEnabled Page 9192 "Company Creation Wizard": * event OnBeforeValidateCompanyType * event OnBeforeValidateCompanyType * event OnOpenPageCheckAdditionalDemoData
Replaced	In addition to making it easier to install rich demo data, this change also enables another improvement. We're loosening up the relatively rigid update policies for major and minor updates that were in place. We're giving administrators extended update periods. For major updates, we're offering five-month update periods to give more time to test and prepare. For example, partners can spread out the workload of updating customer environments, and developers can verify that all apps are compatible. We've also given administrators the ability to opt out of minor updates during a grace period. To learn more, go to Manage environment updates more flexibly.

User groups

Moved, Removed, or Replaced?	Why?
Replaced	User groups are replaced by security groups. Security groups were introduced in Business Central in 2023 release wave 1. They make it easier for administrators to manage user permissions by allowing them to group users by department, job function, and so on. Administrators assign the permissions to the group that its members need to do their jobs. Security groups are based on groups in Microsoft 365 admin center or Azure portal. That benefits administrators because they can use their security groups with other Dynamics 365 apps. For example, if salespeople use Business Central and SharePoint, administrators don't have to recreate the group and its members. To learn more about security groups, go to Control Access to Business Central Using Security Groups.

Moved, Removed, or Replaced?

Why?

Replaced

User groups are replaced by security groups. Security groups were introduced in Business Central in 2023 release wave 1. They make it easier for administrators to manage user permissions by allowing them to group users by department, job function, and so on. Administrators assign the permissions to the group that its members need to do their jobs. Security groups are based on groups in Microsoft 365 admin center or Azure portal. That benefits administrators because they can use their security groups with other Dynamics 365 apps. For example, if salespeople use Business Central and SharePoint, administrators don't have to recreate the group and its members.

To learn more about security groups, go to Control Access to Business Central Using Security Groups.

Changes in 2024 release wave 1

The following features are marked as obsolete:pending in 2024 release wave 1.

Excel reports on the Business Manager and Accountant role centers

Moved, Removed, or Replaced?	Why?
Replaced	The Excel reports (Balance Sheet, Income Statement, Statement of Cash Flows, Statement of Retained Earnings, VAT Collected, Customer Statements, Aged Accounts Payable, and Aged Accounts Receivable) that are available from the Business Manager and Accountant role centers are being replaced by new reports. The new reports use Excel layouts that allow power users to modify the layouts with Excel and upload the new layouts to Business Central. The deprecated reports will be hidden from the role centers in 2025 release wave 1 and will be completely removed from Business Central in 2026 release wave 1.

Moved, Removed, or Replaced?

Why?

Replaced

The Excel reports (Balance Sheet, Income Statement, Statement of Cash Flows, Statement of Retained Earnings, VAT Collected, Customer Statements, Aged Accounts Payable, and Aged Accounts Receivable) that are available from the Business Manager and Accountant role centers are being replaced by new reports. The new reports use Excel layouts that allow power users to modify the layouts with Excel and upload the new layouts to Business Central. The deprecated reports will be hidden from the role centers in 2025 release wave 1 and will be completely removed from Business Central in 2026 release wave 1.

API (v1.0) for Business Central (warning)

Moved, Removed, or Replaced?	Why?
Replaced	With Business Central you can create Connect apps. Connect apps establish a point-to-point connection between Business Central and a 3rd party solution or service using the standard REST API to interchange data. In 2020 release wave 2, we introduced a new improved API where all complex properties are replaced with first-level properties or navigation properties. This change significantly improves API performance, as complex fields were previously calculated at runtime. In API v2.0, all multipart keys and non-GUID keys are replaced with unique GUID keys, and entities can be retrieved using the SystemId, which is immutable, platform-enforced, and indexed. This change improves auditing and API reading performance. We're making the API (v1.0) obsolete in 2024 release wave 1 (to be removed in 2026 release wave 1). The API (v1.0) will be removed in 2026 release wave 1. The API v2.0 contains all the functionality from API v1.0, so migration should be possible. If this isn't the case, reach out to us via https://github.com/microsoft/ALAppExtensions. To learn about the replacement feature, go to Transitioning from API v1.0 to API v2.0.

Moved, Removed, or Replaced?

Why?

Replaced

With Business Central you can create Connect apps. Connect apps establish a point-to-point connection between Business Central and a 3rd party solution or service using the standard REST API to interchange data.

In 2020 release wave 2, we introduced a new improved API where all complex properties are replaced with first-level properties or navigation properties. This change significantly improves API performance, as complex fields were previously calculated at runtime. In API v2.0, all multipart keys and non-GUID keys are replaced with unique GUID keys, and entities can be retrieved using the SystemId, which is immutable, platform-enforced, and indexed. This change improves auditing and API reading performance.

We're making the API (v1.0) obsolete in 2024 release wave 1 (to be removed in 2026 release wave 1).

The API (v1.0) will be removed in 2026 release wave 1.

The API v2.0 contains all the functionality from API v1.0, so migration should be possible. If this isn't the case, reach out to us via https://github.com/microsoft/ALAppExtensions.

To learn about the replacement feature, go to Transitioning from API v1.0 to API v2.0.

Changes in 2023 release wave 2

The following features are marked as obsolete:pending in 2023 release wave 2.

Legacy time sheets experience

Moved, Removed, or Replaced?	Why?
Replaced	You can use time sheets in Business Central to track absence, and to track time and resources that are spent on a project. In 2021 Release Wave 1 we introduced a new experience where we converted time sheet pages to document pages (instead of worksheets). Using document pages lets you access time sheets on mobile devices. We're making the legacy experience obsolete in 2023 Wave 2 (to be removed in 2024 Wave 2) and enabling the new experience as the default for all new customers. To learn about the replacement feature, go to Use Time Sheets.

Moved, Removed, or Replaced?

Why?

Replaced

You can use time sheets in Business Central to track absence, and to track time and resources that are spent on a project. In 2021 Release Wave 1 we introduced a new experience where we converted time sheet pages to document pages (instead of worksheets). Using document pages lets you access time sheets on mobile devices. We're making the legacy experience obsolete in 2023 Wave 2 (to be removed in 2024 Wave 2) and enabling the new experience as the default for all new customers. To learn about the replacement feature, go to Use Time Sheets.

G/L entry aggregations when posting invoices

Moved, Removed, or Replaced?	Why?
Replaced	The Invoice Post. Buffer table is replaced by the use of the Invoice Posting interface. The replacement helps resolve extensibility issues for the legacy Invoice Post. Buffer table. You can now use your own implementation of G/L invoice posting.
If you're a developer and want to learn more about how to extend G/L entry aggregations when posting invoices, go to Extending G/L Entry Aggregations When Posting Invoices.

Exchange Rates Adjustment report

Moved, Removed, or Replaced?	Why?
Replaced	The legacy Exchange Rates Adjustment Report is being replaced by a new capability that increases extensibility and makes it easier to comply with local and industry-specific requirements. It also gives you more control over exchange rate adjustments with a posting preview and how dimension values are post when you adjust exchange rate, and better reporting. To learn more about the new capabilities, go do Adjusting Exchange Rates.

Moved, Removed, or Replaced?

Why?

Replaced

The legacy Exchange Rates Adjustment Report is being replaced by a new capability that increases extensibility and makes it easier to comply with local and industry-specific requirements. It also gives you more control over exchange rate adjustments with a posting preview and how dimension values are post when you adjust exchange rate, and better reporting. To learn more about the new capabilities, go do Adjusting Exchange Rates.

Changes in 2023 release wave 1

The following features are marked as obsolete:pending in 2023 release wave 1.

French, Belgian, and Dutch features for reviewing G/L accounts

Moved, Removed, or Replaced?	Why?
Replaced	Businesses in all countries/regions can benefit from the ability to review general ledger entries before posting them. In a future release, we'll deprecate the country-specific feature and replace it with one that's available in all country versions. After the feature is deprecated, you can use it to access previous reviews, but not to do new reviews. We'll archive your data according to local requirements. To learn about the replacement feature, go to Review Amounts in General Ledger Accounts.

Moved, Removed, or Replaced?

Why?

Replaced

Businesses in all countries/regions can benefit from the ability to review general ledger entries before posting them. In a future release, we'll deprecate the country-specific feature and replace it with one that's available in all country versions. After the feature is deprecated, you can use it to access previous reviews, but not to do new reviews. We'll archive your data according to local requirements. To learn about the replacement feature, go to Review Amounts in General Ledger Accounts.

User groups

Moved, Removed, or Replaced?	Why?
Replaced	User groups let administrators manage permissions for groups of users who have the same or similar roles in the business. For example, you might create a user group for your sales department, and one for your purchasers. To make it a bit easier for administrators to manage permissions, we're replacing user groups and adding the ability to group users directly on permission sets. On the Permission Sets page, use the Users FactBox to assign the set to users. To make it easier to reuse sets of users across other Dynamics 365 apps, we've also introduced optional security groups. Administrators can link Business Central security groups to their counterparts in Microsoft Entra ID or Windows Active Directory. The link let's administrators manage group memberships in Active Directory. In terms of managing permissions, security groups work in the same way as user groups. To learn more about the new security groups, go to Control Access Using Security Groups. If you have an extension that relies on user groups, and you'd like to explore examples of how to update it to use permission sets or Business Central security groups, go to Migrate from User Groups to Permission Sets or Security Groups.

Moved, Removed, or Replaced?

Why?

Replaced

User groups let administrators manage permissions for groups of users who have the same or similar roles in the business. For example, you might create a user group for your sales department, and one for your purchasers. To make it a bit easier for administrators to manage permissions, we're replacing user groups and adding the ability to group users directly on permission sets. On the Permission Sets page, use the Users FactBox to assign the set to users.

To make it easier to reuse sets of users across other Dynamics 365 apps, we've also introduced optional security groups. Administrators can link Business Central security groups to their counterparts in Microsoft Entra ID or Windows Active Directory. The link let's administrators manage group memberships in Active Directory. In terms of managing permissions, security groups work in the same way as user groups. To learn more about the new security groups, go to Control Access Using Security Groups.

If you have an extension that relies on user groups, and you'd like to explore examples of how to update it to use permission sets or Business Central security groups, go to Migrate from User Groups to Permission Sets or Security Groups.

Changes in 2022 release wave 2

Permissions and Permission Set Objects

Moved, Removed, or Replaced? Why?

Replaced In the latest enhancements to composing permissions, the following legacy objects are marked as obsolete:pending and replaced with new ones:

* The Log Table Permissions code unit is replaced by the Log Table Data Permissions codeunit.

* The Permissions page is replaced by the Expanded Permissions page.

* The Tenant Permissions page is replaced by the Permission Set page.

For information about other objects and methods that are being obsoleted, refer to the obsolete reasons in permission management.

Moved, Removed, or Replaced?	Why?
Replaced	In the latest enhancements to composing permissions, the following legacy objects are marked as `obsolete:pending` and replaced with new ones: * The Log Table Permissions code unit is replaced by the Log Table Data Permissions codeunit. * The Permissions page is replaced by the Expanded Permissions page. * The Tenant Permissions page is replaced by the Permission Set page. For information about other objects and methods that are being obsoleted, refer to the obsolete reasons in permission management.

Microsoft SharePoint Connection Setup

Moved, Removed, or Replaced? Why?

Replaced The SharePoint connection setup feature used for OneDrive integration is obsolete and will be removed in 2023 release wave 2 (version 23). In its place, version 21 offers a new guided setup to configure OneDrive integration for system and application features. Learn more about the new setup at Managing OneDrive Integration with Business Central.

The deprecation means that the Microsoft SharePoint Connection Setup page (9551 Document Service Config) is marked as obsolete:pending. However, the platform APIs (in codeunit 9510 Document Service Management) and the document service table that make the legacy functionality possible aren't being deprecated. So any partner solutions that use the APIs directly are unaffected by this change.

Existing customers who are upgrading to version 21, and eventually version 22, can continue to use the legacy SharePoint/Onedrive integration. But we highly recommend that you transition them to the newer OneDrive integration because it's the path going forward. Switching to the newer OneDrive integration setup is a one-way operation, meaning you can't revert to the legacy setup after you've made the switch.

We aspire to resume work on SharePoint integration at a later date.

Moved, Removed, or Replaced?	Why?
Replaced	The SharePoint connection setup feature used for OneDrive integration is obsolete and will be removed in 2023 release wave 2 (version 23). In its place, version 21 offers a new guided setup to configure OneDrive integration for system and application features. Learn more about the new setup at Managing OneDrive Integration with Business Central. The deprecation means that the Microsoft SharePoint Connection Setup page (9551 Document Service Config) is marked as `obsolete:pending`. However, the platform APIs (in codeunit 9510 Document Service Management) and the document service table that make the legacy functionality possible aren't being deprecated. So any partner solutions that use the APIs directly are unaffected by this change. Existing customers who are upgrading to version 21, and eventually version 22, can continue to use the legacy SharePoint/Onedrive integration. But we highly recommend that you transition them to the newer OneDrive integration because it's the path going forward. Switching to the newer OneDrive integration setup is a one-way operation, meaning you can't revert to the legacy setup after you've made the switch. We aspire to resume work on SharePoint integration at a later date.

Bank Reconciliation Worksheet and Deposits in North American versions (US, CA, MX)

Moved, Removed, or Replaced?	Why?
Replaced	We're standardizing the features for reconciling bank accounts and making cash deposits, so that more country versions can benefit from them. For more information, see Standardizing the bank reconciliation process in North American versions. The current features will still allow you to view posted bank reconciliations done through the Bank Rec. Worksheet page, and posted deposits done through the Deposits features, but you can't use these features to create new entries. In October 2023, you must use the Bank Reconciliation page for bank reconciliations. The Bank Rec. Worksheet page won't be available.

Moved, Removed, or Replaced?

Why?

Replaced

We're standardizing the features for reconciling bank accounts and making cash deposits, so that more country versions can benefit from them. For more information, see Standardizing the bank reconciliation process in North American versions. The current features will still allow you to view posted bank reconciliations done through the Bank Rec. Worksheet page, and posted deposits done through the Deposits features, but you can't use these features to create new entries. In October 2023, you must use the Bank Reconciliation page for bank reconciliations. The Bank Rec. Worksheet page won't be available.

Changes in 2022 release wave 1

The following feature is marked as obsolete:pending in 2022 release wave 1.

XBRL reporting

Moved, Removed, or Replaced?	Why?
Removed	Over the years, XBRL has become more than just tagging your financial statement. It's seen improvements in the level of reporting detail, schemas are more flexible in their design, and ESAF has added customization capabilities. This development has meant that the XBRL implementations in the countries/regions we support are diverse, and often complex. For example, taxonomies with hundreds of schema and linkbase files have become the norm. This complexity has made XBRL reporting a task that is better managed by either dedicated software or by service providers. We recommend that you use these service providers. Alternatively, if you have the resources in-house, acquire a dedicated XBRL reporting tool. The XBRL org provides a list of tools and services. For more information, see Tools and Services. Currently, we expect to fully remove support for XBRL in 2023 release wave 1.

Moved, Removed, or Replaced?

Why?

Removed

Over the years, XBRL has become more than just tagging your financial statement. It's seen improvements in the level of reporting detail, schemas are more flexible in their design, and ESAF has added customization capabilities. This development has meant that the XBRL implementations in the countries/regions we support are diverse, and often complex. For example, taxonomies with hundreds of schema and linkbase files have become the norm. This complexity has made XBRL reporting a task that is better managed by either dedicated software or by service providers.

We recommend that you use these service providers. Alternatively, if you have the resources in-house, acquire a dedicated XBRL reporting tool. The XBRL org provides a list of tools and services. For more information, see Tools and Services.

Currently, we expect to fully remove support for XBRL in 2023 release wave 1.

Intercompany Setup page

Moved, Removed, or Replaced?	Why?
Replaced	We have consolidated settings for setting up intercompany capabilities on a single page, and have added a new feature for automatically accepting intercompany transactions in general journals. The current Intercompany Setup page (page 621) is replaced with a new Intercompany Setup page (page 653).

Changes in 2021 release wave 2

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 is removed in 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.

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 use client secret Service-to-Service authentication to connect Business Central with Dataverse 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 client secret Service-to-Service authentication 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.

Moved, Removed, or Replaced?

Why?

Removed

The ability to use client secret Service-to-Service authentication to connect Business Central with Dataverse 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 client secret Service-to-Service authentication 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 is Removed in 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 effect on the Business Central add-in for Outlook, which is described at Using Business Central as your Business Inbox in Outlook.

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. Business Central calculates 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 other 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 AMC's bank data conversion service 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.

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 made the legacy features for personalization and configuring profiles outdated. Therefore, we've 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.

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 occur 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. The document 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 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.

Partager via

Deprecated Features in the Base App

Changes in 2026 release wave 1

API (v1.0) for Business Central (removed)

Legacy Power BI apps on AppSource

Changes in 2025 release wave 1

Excel reports on the Business Manager and Accountant role centres

Legacy Power BI apps on AppSource

Changes in 2024 release wave 2

Configuration packages for setup and evaluation data

User groups

Changes in 2024 release wave 1

Excel reports on the Business Manager and Accountant role centers

API (v1.0) for Business Central (warning)

Changes in 2023 release wave 2

Legacy time sheets experience

G/L entry aggregations when posting invoices

Exchange Rates Adjustment report

Changes in 2023 release wave 1

French, Belgian, and Dutch features for reviewing G/L accounts

User groups

Changes in 2022 release wave 2

Permissions and Permission Set Objects

Microsoft SharePoint Connection Setup

Bank Reconciliation Worksheet and Deposits in North American versions (US, CA, MX)

Changes in 2022 release wave 1

XBRL reporting

Intercompany Setup page

Changes in 2021 release wave 2

Standard APIs, Beta version

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

Legacy Outlook add-in for synchronizing data

Deprecated Features in 2020 release wave 1

Best Price Calculations

Deprecated Features in 2019 release wave 2

The Bank Data Conversion Service

Reports 204-207

User Personalizations and Profile Configurations

Objects that have been marked as obsolete

Breaking Changes

Features that are available only in the online version

Related information

Commentaires

Ressources supplémentaires