Removed or deprecated platform features

This topic describes features that have been removed, or that are planned for removal in platform updates of Finance and Operations apps.

  • A removed feature is no longer available in the product.
  • A deprecated feature is not 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.

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.

Feature removed effective January 28, 2021

Batch job to handle SQL index defragmentation

   
Reason for deprecation/removal In order to reduce the overhead of operating, monitoring, and maintaining the index management by customers, this feature has been removed.
Replaced by another feature? Going forward, the index maintenance will be performed by Microsoft services. This will happen continuously without affecting the user workloads.
Product areas affected Finance and Operations apps
Deployment option Cloud deployment - affects Microsoft-managed production environments and Tier 2 through Tier 5 sandbox environments.
Status This feature is removed.

Platform updates for version 10.0.17 of Finance and Operations apps

Visual Studio 2015

   
Reason for deprecation/removal To support the latest versions of Visual Studio, some changes have to be made to the X++ extensions for Visual Studio. These changes are incompatible with Visual Studio 2015.
Replaced by another feature? Visual Studio 2017 will replace Visual Studio 2015 as the deployed and required version.
Product areas affected Visual Studio development tools
Deployment option All
Status Deprecated. Upon updating, the previous X++ tools will be removed from Visual Studio 2015, and the updated tools will not install on Visual Studio 2015. There is no impact on hosted builds. For build virtual machines, the build pipeline (build definition) needs to be manually updated to change the dependency from MSBuild 14.0 (Visual Studio 2015) to MSBuild 15.0 (Visual Studio 2017) as described in Update a legacy pipeline in Azure Pipelines.

User avatar

   
Reason for deprecation/removal The user avatar that displays on the right side of the navigation bar was retrieved using an API from the Dynamics 365 header control, which has been deprecated.
Replaced by another feature? Users will see their initials in a circle in the navigation bar instead. This is the same visual currently used on development machines.
Product areas affected Web client
Deployment option All
Status Removed as of version 10.0.17

Enterprise Portal (EP) deprecation

   
Reason for deprecation/removal The metadata artifacts associated with Dynamics AX 2012 Enterprise Portal (EP) have been deprecated, as EP was never supported in the Finance and Operations apps.
Replaced by another feature? No
Product areas affected Web client
Deployment option All
Status Deprecated. All EP code is scheduled to be removed in the October 2021 release.

Platform updates for version 10.0.15 of Finance and Operations apps

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.

Visual Studio add-in to apply metadata hotfixes

   
Reason for deprecation/removal Metadata hotfixes are no longer supported with the One Version service updates that were introduced in July 2018 with version 8.1.
Replaced by another feature? Individual metadata hotfixes are not available for supported versions. Cumulative quality updates are applied instead.
Product areas affected Visual Studio add-ins
Deployment option Development virtual machines
Status With version 10.0.15, the add-in is no longer included in the Visual Studio tools.

Platform updates for version 10.0.14 of Finance and Operations apps

Online users page

   
Reason for deprecation/removal This is a legacy page that was built for previous client/server architecture. The information on this page is not always accurate, which can be confusing and misleading.
Replaced by another feature? We will provide a new page in a future update.
Product areas affected System Administration
Deployment option All
Status By October 2021 this form will be removed.

Platform updates for version 10.0.13 of Finance and Operations apps

Custom code defined in SSRS report properties

   
Reason for deprecation/removal In general, custom code offers limited benefits while at the same time, requires significant resourcing and compute to support. Custom code is primarily used by report authors to call public methods from a custom code assembly. However, the cloud-hosted service does not support references to custom assemblies for SSRS reports.
Replaced by another feature? Report authors may choose to continue referencing public .NET APIs for Math, Conversion, and Format operations from any textbox expression. For more information, see Add Code to a Report (SSRS).
Product areas affected Subset of application report designs defined in RDL that contain custom code.
Deployment option All
Status With version 10.0.13, the compiler will begin issuing a warning for instances where custom code is detected in a SSRS report definition. To fix the issue, open the report design definition and remove all custom code artifacts. This warning will be replaced with a compiler error in a future update.

Upgrade of three jQuery component libraries

   
Reason for deprecation/removal Three jQuery component libraries are being updated for security fixes and to maintain currency.
Replaced by another feature? The following libraries are being affected: jQuery (to version 3.5.0 from version 2.1.4), jQuery UI (to version 1.12.1 from version 1.11.4), jQuery qTip (to version 3.0.3 from 2.2.1). Migration guidance has been provided online by jQuery.
Product areas affected Extensible controls, specifically custom JavaScript code utilizing deprecated or removed APIs
Deployment option All
Status With version 10.0.13/Platform update 37, customers can optionally move to the latest libraries by enabling the "Upgrade three jQuery component libraries" feature. Moving to the new libraries will be mandatory with the April 2021 release to allow time for migration of affected APIs.

Existing grid control/forceLegacyGrid() API

   
Reason for deprecation/removal The existing grid control is being replaced by the new grid control.
Replaced by another feature? The new grid control
Product areas affected Web client
Deployment option All
Status In version 10.0.13, the new grid control is generally available, and customers can optionally turn on this feature. The new grid control will become mandatory in the October 2021 release. When the new grid control becomes mandatory, the forceLegacyGrid() API will no longer be honored.

Personalization without saved views

   
Reason for deprecation/removal The personalization subsystem has been overhauled with the saved views feature, so that it has better performance and offers additional capabilities.
Replaced by another feature? Saved views
Product areas affected Web client
Deployment option All
Status In version 10.0.13/Platform update 37, the saved views feature is generally available, and customers can optionally turn on this feature. The saved views feature will become mandatory in the October 2021 release.

Platform updates for version 10.0.12 of Finance and Operations apps

Grid or group control form extensions containing invalid field references

   
Reason for deprecation/removal The data group property on grid or group controls is used to automatically show all the fields of a field group. A grid or group control added by extension could contain fields that are no longer defined on the field group, or it might be missing fields that are defined on the field group. This can cause inconsistent behavior at runtime. Platform updates for version 10.0.12 of Finance and Operations apps now categorize this issue as a compiler warning. To fix this issue, open the form extension and save it.
Replaced by another feature? This compiler warning will be replaced with a compiler error in a future update.
Product areas affected Visual Studio development tools
Deployment option All
Status A compiler warning is introduced in platform updates for version 10.0.12 of Finance and Operations apps.

Platform updates for version 10.0.11 of Finance and Operations apps

Explicit safe lists for self-service environments

   
Reason for deprecation/removal The process for moving IP to safe lists has changed. Self-service no longer supports IP safe lists.
Replaced by another feature? For more information, see Configuring Azure Active Directory Conditional Access.
Product areas affected Security
Deployment option Cloud
Status Deprecated: This feature is fully-deprecated for self-service deployments.

Visual Studio 2015

   
Reason for deprecation/removal To support the latest versions of Visual Studio, some changes have to be made to the X++ extensions for Visual Studio. These changes are incompatible with Visual Studio 2015.
Replaced by another feature? Visual Studio 2017 will replace Visual Studio 2015 as the deployed and required version.
Product areas affected Visual Studio development tools
Deployment option All
Status Virtual machines deployed on version 10.0.13 (Platform update 37) or later contain Visual Studio 2017. Version 10.0.16 (Platform update 40) is the final release with support for Visual Studio 2015. Virtual machines with only Visual Studio 2015 will not be able to update to version 10.0.17 (Platform update 41).

Field groups containing invalid field references

   
Reason for deprecation/removal Field groups in table metadata definitions can contain field references that aren't valid. If these field groups are deployed, they can cause runtime failures in Financial Reporting and Microsoft SQL Server Reporting Services (SSRS). Platform update 23 introduced a compiler warning that enabled this metadata issue to be addressed. Platform updates for version 10.0.11 of Finance and Operations apps categorize this issue as a compiler error.

To fix this issue, follow these steps.

  1. Remove the invalid field reference from the table field group definition.
  2. Recompile.
  3. Make sure that any errors are addressed.
Replaced by another feature? This compiler error permanently replaces the compiler warning.
Product areas affected Visual Studio development tools
Deployment option All
Status Deprecated: The compiler warning is a compiler error in platform updates for version 10.0.11 of Finance and Operations apps.

ISV licenses created by using the SHA1 hashing algorithm

   
Reason for deprecation/removal The process for creating independent software vendor (ISV) licenses has changed. For more information, see Independent software vendor (ISV) licensing.
Replaced by another feature? Yes. Use Windows PowerShell to create licenses.
Product areas affected Visual Studio development tools
Deployment option All
Status Deprecated: ISV licenses that were created by using the SHA1 hashing algorithm. This algorithm depended on certificates that were created by using the MakeCert utility, and this utility has been deprecated.

Deprecated: The use of SHA1 for security or hashing purposes. SHA1 will cease to function in early 2021. Therefore, it should no longer be used.

Removed: Support for Transport Layer Security (TLS) 1.0 and TLS 1.1 incoming or outgoing requests.

Platform update 32

Workflow request change dialog box no longer includes user selection drop-down list

   
Reason for deprecation/removal This was a security issue because the request for change could be sent to an unintended user. This was also a usability issue because it forced the user to determine who the workflow originator was and manually select them.
Replaced by another feature? No
Product areas affected Workflow
Deployment option All
Status The user selection drop-down list was removed from the request change dialog box in Platform update 32. Request change requests will be automatically sent to the originator as intended. For more information about this functionality, see Actions in workflow approval processes.
   
Reason for deprecation/removal Navigation URLs embedded in documents rendered by the service may contain sensitive business data. We are removing support for embedded drill-through links in documents as a security precaution to further protect customer's data. Users will also benefit from improved performance while interactively producing documents as a result of this change.
Replaced by another feature? No
Product areas affected Reporting
Deployment option All
Status This feature is actively being removed from the service.

The modern client offers numerous options for producing views that include auto-generated links to assist in navigating the application. Paginated documents rendered by the service are recommended for external communications that are emailed, archived, and printed for recipients. We have improved the experience for previewing documents directly in the browser, which offers direct access to local printers. For more information, see Preview PDF documents with an embedded viewer.

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.

Note

Can you tell us about your documentation language preferences? Take a short survey.

The survey will take about seven minutes. No personal data is collected (privacy statement).