Removed or deprecated features in Dynamics 365 Commerce

This article describes features that have been removed, or that are planned for removal from Dynamics 365 Commerce.

  • A removed feature is no longer available in the product.
  • A deprecated feature isn't in active development and may be removed in a future update.

This list is intended to help you consider these removals and deprecations for your own planning.

Note

Detailed information about objects in finance and operations apps can be found in the Technical reference reports. You can compare the different versions of these reports to learn about objects that have changed or been removed in each version of finance and operations apps.

Features removed or deprecated in the Commerce 10.0.29 release

Commerce parameters setting - Allow price adjustments to increase product price

   
Reason for deprecation/removal We had this setting to control whether the price adjustment function allows increasing the product price. When this parameter is turned off, when using the price adjustment function organizations can only set a product's unit price lower than its base price and trade agreement sales price. We deprecate this setting because the price adjustment function has been updated to support two-way adjustments (increase or decrease) out of the box.
Replaced by another feature? No
Product areas affected Pricing and discounts
Deployment option All
Status Deprecated: This setting is turned on by default since Commerce version 10.0.29 and will be removed in October 2023.

Commerce parameters setting - Enable price report for retail store

   
Reason for deprecation/removal We had this setting to control whether the price report function is available for use on the store configuration form. We deprecate this setting because the store configuration form has been updated to always provide the price report function as standard function.
Replaced by another feature? No
Product areas affected Pricing and discounts
Deployment option All
Status Deprecated: This setting will be removed in October 2023.

Commerce parameters setting - Use today’s date to calculate prices

   
Reason for deprecation/removal The supply chain management (SCM) pricing engine supports pricing calculation based on the requested ship date or requested receipt date, along with today's date. TheCommerce pricing engine only supports pricing calculation based on today's date. For customers who use both SCM and Commerce capabilities, we provided this setting and recommended that customers always set it to Yes so that the two pricing engines can work together. We deprecate this setting because it doesn't change the calculation behavior and is redundant.
Replaced by another feature? No
Product areas affected Pricing and discounts
Deployment option All
Status Deprecated: This setting is turned on by default since Commerce version 10.0.29 and will be removed in October 2023.

Feature deprecation effective July 2022

Commerce analytics (Preview)

   
Reason for deprecation/removal The Dynamics 365 Commerce team has analyzed the usage and uptake of the Commerce analytics (Preview) feature, and a decision has been made to no longer move forward in bringing the feature to general availability.
Replaced by another feature? At this time, Commerce analytics (Preview) won't be replaced by another feature or solution. The export of raw transactions and master data from finance and operations apps to Azure Data Lake continues to be available, as explained in Export to Data Lake in finance and operations apps. Partners and customers can leverage that data stream to author any intended analytics reports for their business needs.
Product areas affected Commerce analytics (Preview)
Deployment option All
Status We'll be looking at disabling this feature by August 30, 2022. From this date forward, no refreshing will occur in the current Power BI reports provided by Commerce analytics (Preview).

Features removed or deprecated in the Commerce 10.0.21 release

Important

Some or all of the functionality noted in this article is available as part of a preview release. The content and the functionality are subject to change. For more information about preview releases, see One version service updates FAQ.

Overlapping discounts handling setting in Commerce parameters

The Overlapping discounts handling setting on the Commerce parameters page is deprecated in the Commerce version 10.0.21 release. Going forward, the Commerce pricing engine will use a single algorithm to determine the optimal combination of overlapping discounts.

   
Reason for deprecation/removal

The Overlapping discounts handling setting in Commerce parameters controls how the Commerce pricing engine searches and determines the optimal combination of overlapping discounts. It currently offers three options:

  • Best performance – This option uses an advanced heuristics algorithm and a marginal value ranking method to prioritize, evaluate, and determine the best discount combination in a timely manner.
  • Balanced calculation – In the current code base, this option works just like the Best performance option. Therefore, it's essentially a duplicated option.
  • Exhaustive calculation – This option uses an old algorithm that goes through all possible discount combinations during the price calculation. For orders that have large lines and quantities, this option might cause performance issues.

To help simplify configuration, improve performance, and reduce incidents that are caused by the old algorithm, we'll completely remove the Overlapping discounts handling setting and update the internal logic of the Commerce pricing engine so that it now uses only the advanced algorithm (that is, the algorithm behind the Best performance option).

Replaced by another feature? No. We recommend that organizations that use the Balanced calculation or Exhaustive calculation option switch to the Best performance option before this feature is removed.
Product areas affected Pricing and discounts
Deployment option All
Status As of the 10.0.21 release, the Overlapping discounts handling setting will be removed from Commerce parameters in October 2022.

Retail SDK distributed by using Lifecycle Services

The Retail SDK ships in Lifecycle Services (LCS). This mode of distribution is deprecated in release 10.0.21. Going forward, Retail SDK reference packages, libraries, and samples will be published in public repositories on GitHub.

   
Reason for deprecation/removal The Retail SDK ships in LCS. The LCS process takes a few hours to finish, and the process has to be repeated for every update. Going forward, Retail SDK reference packages, libraries, and samples will be published in public repositories on GitHub. Extension samples and reference packages can be consumed easily, and the updates finish in a few minutes.
Replaced by another feature? Download Retail SDK samples and reference packages from GitHub and NuGet
Product areas affected Retail SDK
Deployment option All
Status Deprecated: As of release 10.0.21, the SDK shipped via the LCS VMs will be removed in October 2023.

Retail deployable package and combined POS, Hardware station, and Cloud Scale unit installers

Retail deployable packages generated using the Retail SDK MSBuild is deprecated in 10.0.21. Going forward, use the Cloud Scale Unit (CSU) package for Cloud Scale unit extensions (Commerce Runtime, channel database, Headless commerce APIs, Payments, and Cloud Point of Sale (POS)). Use extension-only installers for POS, Hardware station, and Cloud scale unit self-hosted.

   
Reason for deprecation/removal A Retail deployable package is a combined package that contains a complete set of extension packages and installers. This combined package makes the deployment complex, as CSU extensions go to Cloud scale unit and installers are deployed in stores. The installers include the extension and base product, which makes the updates difficult. With every upgrade, a code merge and package generation are required. To simplify this process, the extension packages are now separated into components for easy deployment and management. With the new approach, extensions and base product installers are separated and can be independently serviced and upgraded without a code merge or repackaging.
Replaced by another feature? CSU extensions, POS extension installers, Hardware station extension installers
Product areas affected Dynamics 365 Commerce extension and deployment
Deployment option All
Status Deprecated: As of release 10.0.21, support for deploying RetailDeployablePackage in LCS will be removed in October 2022.

For more information, see:

ModernPos.Sln and CloudPos.sln in the Retail SDK

POS extension development using ModernPos.sln, CloudPos.sln, POS.Extension.csproj, and the POS folder is deprecated in release 10.0.21. Going forward, use the POS-independent packaging SDK for POS extensions.

   
Reason for deprecation/removal In earlier versions of the Retail SDK, if there are POS extensions, a code merge and repackaging is required to update to the latest version of the POS. The code merge was a time-consuming upgrade process and you had to maintain the full Retail SDK in the repository. You also had to compile the core POS.App project. By using the independent packaging model, you must maintain only your extension. The process of updating to the latest version of the POS extensions is as easy as updating the version of the NuGet package that your project consumes. Extensions can be deployed independently, and services use the extension installers. The base POS can be deployed and maintained separately, and no code merge or repackaging with the base installer or code is required.
Replaced by another feature? POS-independent packaging SDK
Product areas affected Dynamics 365 Commerce POS extension and deployment
Deployment option All
Status Deprecated: As of release 10.0.21, support for combined POS packages and extension model using the ModernPos.Sln, CloudPOs.sln, and POS.Extensons.csproj in Retail SDK will be removed in October 2023.

Features removed or deprecated in the Commerce 10.0.17 release

Full dataset generation interval is deprecated

   
Reason for deprecation/removal Beginning in this release, in the Commerce scheduler parameters form in Dynamics 365 headquarters, the Full dataset generation interval in days field will be deprecated. Also starting in this release, the field will be visually removed so that the value can't be edited. This will stay as the value 0.
Replaced by another feature? No
Product areas affected Dynamics 365 Commerce
Deployment option All
Status Deprecated. Don't use this field or change the value in it.

Features removed or deprecated in the Commerce 10.0.15 release

Internet Explorer 11 support for Dynamics 365 is deprecated

   
Reason for deprecation/removal Effective December 2020, Microsoft Internet Explorer 11 support for all Dynamics 365 products is deprecated, and Internet Explorer 11 won't be supported after August 2021.

This will impact customers who use Dynamics 365 products that are designed to be used through an Internet Explorer 11 interface. After August 2021, Internet Explorer 11 won't be supported for such Dynamics 365 products.
Replaced by another feature? We recommend that customers transition to Microsoft Edge.
Product areas affected All Dynamics 365 products
Deployment option All
Status Deprecated. Internet Explorer 11 won't be supported after August 2021.

Features removed or deprecated in the Commerce 10.0.11 release

Data action hooks

   
Reason for deprecation/removal The data action hooks feature has been deprecated due to performance issues.
Replaced by another feature? We recommend using data action overrides to modify business logic in the data action layer.
Product areas affected e-Commerce extensibility data actions
Deployment option All
Status Deprecated: As of release 10.0.11

Retail SDK support for Visual Studio 2015, msbuild 14.0, and Retail SDK\Reference libraries and tools

   
Reason for deprecation/removal Retail SDK support for Visual Studio 2015 has been deprecated and updated to support VS 2017, msbuild 15.0 and all the reference libraries and commerce proxy generator tools in the RetailSDK\References folder moved to NuGet packages to simplify the extension model and SDK upgrade process.
Replaced by another feature? We recommend that you follow the information in Migrate the Retail SDK from Visual Studio 2015 to Visual Studio 2017 to update your system.
Product areas affected Retail SDK extensions
Deployment option All
Status Deprecated: As of release 10.0.11

Retail Server Extension using IEdmModelExtender and CommerceController

   
Reason for deprecation/removal Retail server extension using IEdmModelExtender and CommerceController has been deprecated to provide simplified extension model. The new implementation will have only the controller class without any additional IEdmModelExtender class implementation. This also avoids the dependency with a particular OData version (if the OData version is updated it may break extensions.)
Replaced by another feature? We recommend that you use the IController class extension model by importing the NuGet (Microsoft.Dynamics.Commerce.Hosting.Contracts) package.
Product areas affected Retail server extensions
Deployment option All
Status Deprecated: As of release 10.0.11

Hardware station Extension using IHardwareStationController

   
Reason for deprecation/removal Hardware station extension using IHardwareStationController has been deprecated to provide simplified extension model. The new implementation will have only the IController class without any additional class implementation and to avoid the dependency with core hardware station libraries, previously extension need to refer multiple libraries.)
Replaced by another feature? It's recommended to use the IController class extension model by importing the NuGet (Microsoft.Dynamics.Commerce.Hosting.Contracts) package.
Product areas affected Hardware station extensions
Deployment option All
Status Deprecated: As of release 10.0.11

Features removed or deprecated in the Commerce 10.0.10 release

POS operation 803 - Picking and receiving

   
Reason for deprecation/removal Picking and receiving operations is being deprecated due to new operation redesign.
Replaced by another feature? Yes. It's replaced by two new POS operations: inbound operation (804) and outbound operation (805).
Product areas affected Point of sale (POS) application
Deployment option All
Status Deprecated: As of release 10.0.10, the picking and receiving operation will no longer receive any new feature updates. Only critical bug fixes will be done for this operation in future releases. All customers are encouraged to move to the new Inbound operations and Outbound operations, which will continue to be part of our long-term product roadmap.

Features removed or deprecated in the Commerce 10.0.7 release

Commerce GetProductAvailabilities and GetAvailableInventoryNearby APIs

   
Reason for deprecation/removal New optimized APIs have been created to replace the GetProductAvailabilities and GetAvailableInventoryNearby APIs.
Replaced by another feature? Yes: It's replaced by GetEstimatedAvailabilty and GetEstimatedProductWarehouseAvailability APIs.
Product areas affected e-Commerce application SDK
Deployment option All
Status Deprecated: As of release 10.0.7, there will no longer be engineering investments made for GetProductAvailabilities and GetAvailableInventoryNearby. Organizations that use these APIs in their e-Commerce deployments should convert to the new GetEstimatedAvailabilty and GetEstimatedProductWarehouseAvailability APIs and enable the Optimized product availability calculation feature.

Previous announcements about removed or deprecated features

To learn more about features that have been removed or deprecated in previous releases, see Removed or deprecated features in previous releases.