Service Update 64 for Microsoft Dynamics 365 9.1.0


INTRODUCTION


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

Starting October 5, 2019, we will enable the 2019 release wave 2 features (end user impacting only) across our global customer base. Your environment/organization will be updated during one of the maintenance windows over a weekend. For more information, click here.

Please note that our naming conventions have changed to clarify the link between the version number and service update.  For example, Service Update 64 will correspond to version number 64XX. 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 64 for Microsoft Dynamics CRM Online 9.1.0 9.1.0.6431


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 64 resolves the following issues:

Performance Improvements

The following list details performance improvements made to Dynamics.

  • Improved lock contention in time zone related methods.

Unexpected Behavior

The following list details issues whose resolutions correct actions performed in Dynamics that do not work as intended.

  • When creating an activity (email, appointment, etc.) the main form loaded instead of the QuickCreate form.
  • SLAs were set as "Success" if the success condition was met, even when the SLA deadline was missed.
  • When tabbing to a checkbox in a grid, the JAWS 2019 screen reader software announced "Row read only required" instead of something like "Row Checkbox not checked".
  • After using a direct link to navigate to a new page, and then refreshing the page, the browser refreshed to the first page, not the directly accessed page.*

Repaired Functionality

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

  • Report data did not auto refresh.
  • Updates made in associated records by a plugin while in offline mode did not reflect when in online mode.
  • The names of project entity records did not update in the Activities grid when changed.*
  • The ribbon command bar was missing when adding a new SLA item.*
  • A custom URL used to direct users to a help page was not functioning in Unified Interface.
  • An error message displayed with unneeded special characters in place of a line break.
  • Opportunities that were closed in Unified Interface reflected as "closed" but not also as "cancelled".
  • The mailbox ribbon did not display in Unified Interface.*
  • All of an entity's columns were retrieved when an audited entity with no auditable attributes was updated.*
  • Notes and/or posts were not visible in Unified Interface when the user did not have sufficient privileges on the Systemuser entity but did have sufficient privileges on the Notes and/or Posts entity.
  • No progress indicator displayed when uploading a large Excel template file.
  • The Custom Help URL link in the system settings did not function.*
  • Appointments created using the Web client displayed a "Scheduled" status, while appointments created using Unified Interface displayed an "Open" status.
  • Users could not create or edit their own existing email templates.*
  • A new model driven app did not load the correct sitemap in Unified Interface.
  • JavaScript controls could not be added to the header fields of a business process flow.
  • When uploading a large Excel template file, no progress indicator displayed.*
  • Appointments' Regarding field value did not automatically populate in Unified Client.
  • The page reloaded continuously when the "Assign user role" button was selected.*
  • The Regarding Object column in the Activities grid did not reflect changes to project record names.*
  • When filtering the Account field in the New Opportunity form twice, based on entered text, the results for the second filter were not updated from the first filter's results.*
  • Lookups loaded slowly.
  • When an email containing an attachment was sent using an SMTP based email server profile, the attachment's file size was 0 bytes.*
  • The names of project entity records did not update in the Activities grid when changed.*
  • The order in which optionsets were displayed could not be changed.*
  • 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.*
  • The Business Unit field could not be mapped in the Field Mapping window when importing data.
  • Changes to unspecified AM/PM designators could not be saved. PM values resulted from selecting AM values.*

Error Messages, Exceptions, and Failures 

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

  • Importing a solution failed with errors.
  • When a solution containing custom fields and the Activities check enabled failed with an error ("Invalid column name failure").*
  • A JavaScript error occurred when opening any product.
  • An error occurred ("Error loading control") when the Show Global Filter link was selected, followed by the "Valore Totale Ok" link.
  • An error occurred when associating an entity with system users using the Ownerid field.*
  • An generic error occurred when loading the Document Associated Grid.
  • Workflows used to send or update emails failed if the Subject field length exceeded 200 characters.*
  • Solutions containing a business process flow with a long name could not be imported or created.*
  • When in multi session, an "Error loading control" message displayed in new forms.*
  • An error occurred when a record's owner ID was associated. (Error: "edmProperty should be CrmEdmStructuralProperty")*
  • The Timeline control failed to load when opening the Account record.*
  • Unexpected 403 errors occurred when loading various entity forms.
  • An error occurred when a mailbox was configured without a unified principal name (UPN).
  • An unintelligible error displayed when assigning a record with unfilled required fields.
  • An error occurred when creating an entity with a name that exceeded 50 characters. (Error: A string value provided is too long.)

Return to Release List

If you have any feedback on the release notes, please provide your thoughts here.