Dynamics 365
Introduction
Service Update 9.1.5 for Microsoft Dynamics CRM (on-premises) 9.1 is now available. This article describes the hotfixes and updates that are included in Service Update 9.1.5.
More information
|
Update package |
Version Number |
|---|---|
|
Service Update 1.5 for Microsoft Dynamics CRM (on-premises) 9.1 |
9.1.5.25 |
To determine whether your organization had this update applied, check your Microsoft Dynamics CRM Online version number. Select the gear icon in the upper-right corner, and then select About.
Update information
Microsoft Dynamics 365 (on-premises) Update 1.5 is now available.
The following file is available for download from the Microsoft Download Center:
Download the Microsoft Dynamics 365 (on-premises) Update 1.5 package now
Service Update 1.5 resolves the following issues
Repaired functionality
The following list details items in Dynamics that were not functioning but are now repaired:
-
Certain "Invalid object name" errors that are handled and result in no impact on application functionality were still logged as errors, which could result in writing large quantities of false-positive errors to the Windows Event Log on backend servers.
-
Customers were not able to view GUID datatype attribute in the workflow designer.
-
Labels in Lookup Record popup screen is displayed in multiple lines in certain version of browsers.
-
When Dynamics attempts to re-index / de-fragment the indexes in the database, the re-indexing script can fail with a table not found exception causing the indexes to be more fragmented and take more space.
-
When "Existing Product" field erased and toggle the “Pricing” field on the "QUOTE PRODUCT" form results into script error.
-
When a post with a mention is created on the backend using an Entity Type Name ("contact"/"systemuser"/etc) instead of a code type value in the form of an integer, the link created in unable to be navigated to when clicked.
-
The Activities Patch solution is not getting installed with version upgrade.
-
Security fixes.
Note: An asterisk (*) at the end of a fix statement denotes that this repair item was incorporated into multiple service update releases.
