INTRODUCTION
Service Update 44 for Microsoft Dynamics CRM Online 9.1.0 is now available. This article describes the hotfixes and updates that are included in Service Update 44.
Please note that our naming conventions have changed to clarify the link between the version number and service update. For example, Service Update 44 will correspond to version number 44XX. 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 44 for Microsoft Dynamics CRM Online 9.1.0 |
9.1.0.4441 |
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 44 resolves the following issues:
Unexpected Behavior
The following list details issues whose resolutions correct actions performed in Dynamics that do not work as intended.
-
An extra column appeared when a field was hidden.
-
When refreshed, forms displayed on the Web with an inconsistent hybrid of the 8.2 version style and the 9.0 version style.*
-
Phone Call tasks marked "complete" in Dynamics 365 reopened automatically.
-
The Product grid was not editable when switching its view setting back and forth to "inline edit view".
-
The Product grid was not editable when switching its view setting back and forth to "inline edit view".
Repaired Functionality
The following list details issues whose resolutions repair items in Dynamics that are not functioning.
-
Business Unit could not be deleted.
-
Contacts could not be added to an account record.
-
Appointments synced using server-side synchronization (SSS) did not contain line breaks.
-
Dateline fields were unsorted in comparison charts.
-
The business process flow could not be switched unless the record was saved in Unified Client and the page was refreshed.
-
Selecting an element from a Lookup control sometimes resulted in a blank white screen.
-
Appointment time zones in Dynamics 365 changed to UTC.*
-
Sequence numbers were duplicated when changing the sequence number of rule items to anything other than "1", resulting in data corruption.*
-
Teams could not be accessed from field security profiles.
-
Opportunities and qualify leads could not be created when updating a business process flow instance by running a synchronous workflow.
-
Audit history was missing from Unified Client custom entity records.
-
The wrong date/time values displayed for users in the Montevideo time zone (GMT -03:00).
-
Custom views could not be used with the lookup view picker in Unified Client.
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 accessing the mobile Dynamics 365 app. (Error: Not able to retrieve in local store with logicalname 'activityparty')
-
Multiple scenarios resulted in a SQL error: "Invalid column name 'OwnerId'.*
-
An error prevented users from finding avaialble times for resources without selecting a resource for a service. (Error: Web Service Plug-in failed..)
-
An error occurred when adding a new field to the "Phone Call2" entity. (Error: Violation of primary key constraint.)
-
Root execution content failed to null out when an async operation was completed.
-
An error occurred when opening the cases view from the Entitlement page.
-
An error appeared when the Phone field was changed.
-
When opening an appointment, an error occurred preventing users from viewing calendar activities. (Error: Something has gone wrong..)
If you have any feedback on the release notes, please provide your thoughts here.
