Skip to content
Dynamics 365 Blog

Applies to: Field Service version 8.8.1.45 on Dynamics 365 for Customer Engagement version 9.x

Visit the Admin Center for Dynamics 365 solutions page to install the update. For details, refer to how to install or update a preferred solution.

Please visit Field Service Docs for Field Service updates and related content.

Field Service enhancements

Enhancements

  • Improved requirement naming for requirements which are part of a requirement group and related to a work order.
  • Improved upgrade behaviors.
  • Performance enhancements.

Bug Fixes

  • Fixed: When generating a work order from an Agreement Booking Setup, msdyn_unit should be null checked as it is not a required field.
  • Fixed: Requirement Group Name is empty when created from Workorder Incident Type.
  • Fixed: Enable overriding field value of msdyn_generatewodaysinadvance in AgreementBookingSetup.Library.js.
  • Fixed: Fix misleading error message for multi-level security permission exception.
  • Fixed: Not able to select address from address suggestion box in account/contact in web client.
  • Fixed: Time Zone Conversion check for invoiceDateGeneration Logic to be in sync with AgreementBookingDate logic.
  • Fixed: IOT device registration message field.
  • Fixed: Estimate Unit Amount and Unit Amount fields not getting populated automatically.
  • Fixed: Generate Booking Dates workflow is not reset when Agreement Booking Setup is modified by a user in a different Business Unit.
  • Fixed: Cannot save Work Order after change System Status to ‘Closed – Posted’ if ~350 invoice products exist.
  • Fixed: Filtering for the Customer Asset look-up on Work Order does not update when changing the service account.
  • Fixed: Add null check in AgreementInvoiceProductOperation.cs for better telemetry/logging.
  • Fixed: Address suggestions doesn’t populate the address correctly when multiple addresses are returned.

Connected Field Service (CFS) enhancements

Enhancements

  • New flow templates for CFS integration with Azure IoT Central that utilizes the Common Data Service (CDS) connector in flow. The CDS connector are available in the new Dynamics datacenter regions and has improved performance and reliability compared to the existing Dynamics 365 connector.
  • For CFS with IoT Hub, new deployments will now utilize the CDS connector in the logic app.

 

Bug Fixes

  • Fixed: Hide Send Command in Customer Asset if there are no connected devices.
  • Fixed: When an IoT device registration fails, the error message displayed is not appropriate.
  • Fixed: Logic app designer view in Azure is grayed out. Upgrading through deployment app, will install the new logic app template that allows the designer view.
We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!

Join the conversation

Add comment

Leave a Reply

Your email address will not be published. Required fields are marked *

I understand by submitting this form Microsoft is collecting my name, email and comment as a means to track comments on this website. This information will also be processed by an outside service for Spam protection. For more information, please review our Privacy Policy and Terms of Use.

Loading comments...