Platform updates for version 10.0.16 of finance and operations apps (February 2021)

This article lists the features that are included in the platform updates for version 10.0.16 of finance and operations apps. This version has a build number of 7.0.5860 and is available on the following schedule:

• Preview of release: November 2020
• General availability of release (self-update): January 2021
• General availability of release (auto-update): February 2021

Features included in this release

The following features are included in this release. Some of the listed features are still in preview, while others may already be generally available. See the release plan for official release dates for each feature.

• User session management
  - Administrators have the ability to set a maximum session timeout for individual users. The range of the session can be from 1 hour to 2160 hours. When this session length expires, the user is required to sign in with their credentials. For more information, see User session management.

• Renamed 'Session idle timeout' to 'Session inactivity timeout'
  - To differentiate the types of session timeouts between maximum user session and inactivity user session, a change in the name was implemented. For more information, see Set the session inactivity timeout.

• Removing support for Visual Studio 2015
  - Version 10.0.16 is the last version to support Visual Studio 2015. For more information, see Removing support for Visual Studio 2015.

• Email throttling
  - This feature allows non-interactive email providers to adhere to a per-minute email sending limit, which prevents errors that are currently triggered when the system attempts to send more emails than the provider can handle. When email throttling is enabled, sending limits for Microsoft 365 email providers will be set automatically; manual configuration is required for all other email providers. For more information, see Configure and send email.

• Document (attachment) history
  - This document management feature creates a history mechanism for record attachments. This allows your organization to maintain an audit of actions related to individual attachments. For example, you can see when an attachment was created, marked for pending deletion, restored, deleted, or moved and who performed the action. The default history retention period is 180 days, however this is configurable on the Document management parameters page. For more information, see Configure document management.

• General availability of the Grouping with grids feature
  - For more information, see Grid capabilities.

• New HTML editor control
  

• Enhanced the Message::AddAction API
  - The Message::AddAction API now surfaces the action in notifications when messages are routed to the Action center or Message details pane. For more information, see Messaging APIs.

• Mitigate a SQL injection attack
  - Use the new Statement.executeQueryWithParameters API to mitigate SQL injection attacks.

Most of these features must be enabled using Feature management before you can use them.

Additional resources

Bug fixes

For information about the bug fixes that are included in this update, sign in to Microsoft Dynamics Lifecycle Services (LCS), and view the KB article.

Dynamics 365: 2020 release wave 2 plan

Wondering about upcoming and recently released capabilities in any of our business apps or platform?

Check out the Dynamics 365: 2020 release wave 2 plan. We've captured all the details, end to end, top to bottom, in a single document that you can use for planning.

Removed and deprecated platform features

The Removed or deprecated platform features article 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 isn't in active development and might be removed in a future update.

A deprecation notice will be added in the Removed or deprecated platform features article 12 months before the removal of any feature from the product.

For breaking changes that affect only compilation time, but that are binary-compatible with sandbox and production environments, the deprecation time will be less than 12 months. Typically, these changes are functional updates that must be made to the compiler.