Microsoft Dynamics 365 - Service Update 21012 Release Notes

Article
05/17/2022

Service Update 21012 for Microsoft Dynamics 365 9.1.0 is now available. This article describes the hotfixes and updates that are included in Service Update 21012.

Important

Note: Service Update naming convention has been revised to clarify the link between the version number and Service Update number. For example, Service Update 150 will now correspond to version number 150xx. Occasionally a Service Update will be canceled and all associated fixes will be rolled into a subsequent Service Update. For this reason, Service Update numbers may not always increase incrementally.

Update package	Version number
Service Update 21012 for Microsoft Dynamics 365 9.1.0	9.2.21012.00154

To determine whether your organization had this update applied, check your Microsoft Dynamics 365 version number. Click the gear icon in the upper-right corner, and then click About.

An (*) at the end of a fix statement denotes that this repair item was incorporated into multiple service update releases.

Service Update 21012 resolves the following issues:

Repaired Functionality

The following list details issues whose resolutions repair items in Dynamics that are not functioning.

Accessibility

When zoomed to 200%, keyboard focus was applied to the top of the page after closing the expanded sorting options.*
The "Bulk Delete" option did not contain unique title labels and were not announced by the accessibility narrator.
The accessibility screen reader did not announce the correct number of tables in the Tables list.*
When modifying advance setting options and using keyboard navigation, keyboard focus was not applied to the first possible selection.
The Share, Bulk Edit, and Personalization Setting control type options did not contain unique title labels and were not announced by the accessibility screen reader.
When using keyboard navigation within the Common Tasks section, keyboard focus was not visible in the Marketing app.
The accessibility screen reader described the "delete" option in the "confirm deletion" dialog box as "cancel" when its control type should be a link.
The accessibility screen reader described the "Currency Format" and "Negative Currency Format" options contained as a "list" control type label instead of a combo box.
When modifying the Synchronization Settings, the screen reader could not describe the combo box for the "Group or" button because it did not have a name property.
When sharing an account dataset, the accessibility screen reader announced a blank column and did not announce the header content.
In the Customer Service Hub, focus was not applied to the column headers within the Audit history dataset.*
The accessibility screen reader did not announce "Checked/Unchecked" after selecting the “Select All” check box present on the “Look up records” window.
The Share, Bulk Edit, and Personalization settings options did not contain title labels and were not announced by the accessibility narrator.
The accessibility screen reader did not announce the text content within the "confirm deletion" dialog box header.
The accessibility screen reader did not apply focus to the "apply-" button when modifying personalization settings.
The accessibility screen reader did not understand multiple control types within the Sales App as they were labelled as buttons rather than links.
The content header option did not contain a title label and was not announced by the accessibility narrator.
When using a filter in a currency dataset, focus was applied twice to a checkbox for each option.
The accessibility screen reader did not announce the instructions for using the sort button in the “Status Reason” column header.
When creating a new chart, the accessibility narrator announced the add a series/add a category button twice.
The accessibility screen reader would not announce the full name in a header if focus was shifted to the Expand/Collapse button.
The accessibility screen reader announced all the page navigation options at once while using keyboard navigation within the “Email Templates” tab.
The accessibility screen reader announced the incorrect selected/unselected state of the Activities tab.
When selecting the "confirm" button in a Bulk Assign dialog box, keyboard focus was applied to options outside of the box.
When using keyboard navigation, keyboard focus did go in a logical order on the dashboard.
The accessibility screen reader did not announce the heading markup for the "Business" header text.
The accessibility screen reader did not announce the state of the "Select/clear all records" option and announced an incorrect control type.
The accessibility screen reader announced all page navigation options at once while using keyboard navigation within the “Email Templates” tab.
The accessibility screen reader did not distinguish between the header content and normal text within the Marketing app.
When using keyboard navigation, focus could not be applied to the “All” button when selecting users as a record type within an email.
When using keyboard navigation, focus could not be applied to the “All” button within expanded lookup records.
The accessibility screen reader did not announce when the "more action" dropdown menu changed to an expanded or collapsed state.
The accessibility screen reader did not understand multiple control types on the Dashboard as they were labelled as buttons rather than links.
The alternate text for "Incident" in the Customer Service Hub was not localized when in tile view.*
The accessibility screen reader did not apply focus to the "apply" button when modifying personalization settings.

Platform Services

When creating an appointment with Rich Text settings and synchronizing with Exchange, the text content was modified to the simple text format.*
Entity string attributes could not be set to localizable.

Sales

When exporting a Notes entity record to Excel using Advanced Find, the description section text content was replaced by HTML tags.*
When creating a folder from an account entity in SharePoint, alphabetical name characters were converted to dash symbols.

Solutions

In the Customer Service Hub, resource details within the within the service calendar contained only one column for all available views.

Unified Interface

The "facet" search filter, when performing a relevance search in an organization with the Arabic language setting, was not functioning in iOS.
Stage navigation was unresponsive when opening a record containing a Business Process Flow (BPF) while in offline mode.*
When using keyboard navigation, focus did not go to the correct menu items within the Customer Service Hub.
In the timeline, phone call activity records could not be expanded and did not contain a description section.*
The sort action did not sort records within the Accounts/Contacts grid.*
When utilizing keyboard navigation within Account records, the item in focus was not displayed in the correct color.*
When utilizing keyboard navigation within Account records, the back button could not be accessed.*
When creating an email with a regarding field and tracking, the email did not have a recipient card or a regarding card in the Dashboard.*
The ellipsis menu on apps in the My Apps page incorrectly displayed "Show for all roles" instead of "Hide for all roles."
The heading size HTML tag for the "My Open Cases" option was incorrect, which prevented screen reader navigation using heading tags.
Grid controls did not load when using an RTL (Right-to-Left) language.
When closing a case in the incident resolution activity in timeline, the case status was changed to "resolved by" instead of "case resolved by" in the timeline.
The "Next 30 days" filter under the activity due date filter within the timeline did not filter the correct results.
The search flyout in the header would drop down randomly when entering data in a form.*
The recipient and regarding cards were missing within the MailApp dashboard.*
The ‘From’ and ‘To’ field values were not visible, intermittently, within an activities view.*
Standalone records created within the App Designer for Business Process Flows with no primary entity and added to the site map would fail to load.
Lookup fields could not be edited when browser zoom was set to 90%.*

Error Messages, Exceptions, and Failures

The following list details issues whose resolutions correct actions that produce errors, unhandled exceptions, or system or component failures.