INTRODUCTION
Service Update 60 for Microsoft Dynamics CRM Online 9.1.0 is now available. This article describes the hotfixes and updates that are included in Service Update 60.
Please note that our naming conventions have changed to clarify the link between the version number and service update. For example, Service Update 60 will correspond to version number 60XX. Occasionally a Service Update will be canceled and all the associated fixes will be rolled into the next Service Update, thus Service Update numbers will not always increase incrementally.
As this release is deployed globally, we will continue to add fixes and the version number may change. Check this article regularly as we continue to document fixes added to this release.
MORE INFORMATION
Update package |
Version number |
---|---|
Service Update 60 for Microsoft Dynamics CRM Online 9.1.0 |
9.1.0.6014 (or higher) |
To determine whether your organization had this update applied, check your Microsoft Dynamics CRM Online version number. Click the gear icon in the upper-right corner, and then click About.
Please note that an (*) at the end of a fix statement denotes that this repair item was incorporated into multiple service update releases.
Service Update 60 resolves the following issues:
Unexpected Behavior
The following list details issues whose resolutions correct actions performed in Dynamics that do not work as intended.
-
A product's sequence number in a bundle didn't change when the sequence number of the bundle itself changed.
Repaired Functionality
The following list details issues whose resolutions repair items in Dynamics that are not functioning.
-
Unified Client's View Hierarchy button did not function for contacts who were part of an account's organization chart.
-
While offline, grids did not load when they contained created or modified fields.
-
Records were not displayed under the subgrids in the Project entity under the sales module for a particular record.
-
Activities did not appear in the lead record timeline when the lead was present in the Activity Party field but not in the Regarding field.
-
When attempting to hide a section within a tab in Unified Client, the section was not hidden if the session contained a field that was referred in a business rule.
-
When performing a bulk delete operation, the displayed number of selected items was greater than the actual number of items selected.
-
A subgrid's view selector did not display when a chart was added.
-
An attachment element added to the Note entity did not display when accessing Dynamics 365 from an iOS device.
-
Work orders could not be created.
-
The view of the Holding Account business process flow (BPF) could not be filtered in the header fields of the Case process flow BPF.*
-
Some entity forms hung indefinitely with a "Loading Business Logic" message until the user refreshed the page with Ctrl+F5.
-
An error "edmProperty should be CrmEdmStructuralProperty" displayed when an entity was associated with the system users using the OwnerId field.*
-
The order in which optionsets were displayed could not be changed.*
-
Business process flow (BPF) stage navigation did not function when it contained an action step.*
-
Added charts did not display, or they displayed with default Y-Axis label values.*
-
The TimeControl dropwn did not expand when the TimeControl value was set to "---".
-
Appointment start times and end times could not be changed in Unified Client.
-
Duplicate queue items with the same source entity ("test case 1") were created when that entity was added to any queue.
-
When changes were made to multiple Quote line items, some of those changes did not go through.
-
Contracts containing an email address stopped synchronizing when the email address was removed.
Error Messages, Exceptions, and Failures
The following list details issues whose resolutions correct actions that produce errors, unhandled exceptions, or system or component failures.
-
An error occurred when syncing multiple email accounts in the Dynamics 365 App for Outlook.
-
An error occurred when viewing a case resolution record's audit history.
-
Authentication failed for mailboxes configured with users without user principal names.
-
The Timeline control did not load when accessing the Account record. (Error: Cannot read property 'DisplayName' of undefined.")
-
A 409 error occurred when synchronizing data on organization with 64-bit metadata versions.
-
An error occurred when selecting the Email a Link command button. (Error: You have exceeded the maximum number of {0} characters in this field.) --- When selecting an "Email a Link" command button the following error occurred "Error: You have exceeded the maximum number of {0} characters in this field".
If you have any feedback on the release notes, please provide your thoughts here.