Field Service version history

Latest version availability

Solution Latest version Download links
Field Service 8.8.+ Upgrade or create a new trial
Field Service Mobile 12.1.+ Windows, iOS, and Android
Mobile Configuration Tool (Woodford) 12.1.+ Direct download link (English only)
Mobile Project Template 1.0.4549 Direct download link (English only)

Release For information about other updates to Field Service, visit the Dynamics 365 Release Plans.

Region Current Version Next Version Scheduled Date
Station 2
South America 8.8.22.57 8.8.23.52 05/29/20
Canada 8.8.22.57 8.8.23.52 05/29/20
India 8.8.22.57 8.8.23.52 05/29/20
France 8.8.22.57 8.8.23.52 05/29/20
United Arab Emirates 8.8.22.57 8.8.23.52 05/29/20
South Africa 8.8.22.57 8.8.23.52 05/29/20
Germany 8.8.22.57 8.8.23.52 05/29/20
Station 3
Japan 8.8.22.57 8.8.23.52 06/05/2020
Asia Pacific 8.8.22.57 8.8.23.52 06/05/2020
Great Britain 8.8.22.57 8.8.23.52 06/05/2020
Oceana 8.8.22.57 8.8.23.52 06/05/2020
Station 4
Europe 8.8.22.57 8.8.23.52 06/12/2020
Station 5
North America 8.8.22.57 8.8.23.52 06/19/2020
Station 6
Government Community Cloud 8.8.11.19 8.8.12.2 05/29/2020
China 8.8.11.19 8.8.12.2 05/29/2020

Note

While most updates should be complete on the scheduled night, updates requiring more time may be completed during dark hours of the weekend indicated in the Scheduled Date column.

8.8.23.52

(Includes Universal Resource Scheduling version 3.12.22.8)

  • Improved Crew booking validations which ensure that the booked crew has at least one defined crew member for the date on which the booking is being created.
  • Improved descriptions in upgrade scripts to make the script more comprehensible by an administrator by documenting deprecated upgrade script steps to minimize confusion.
  • Fixed an issue which left the status null when created a new geofence which could cause geofence events not to be created.
  • Repaired a field service upgrade issue caused by a script that, when appropriate, created requirement group records. If the requirement group’s name was too long, the script and upgrade would fail.
  • Fixed an issue on the Contact entity’s geo code functionality which caused a script error if “Auto Geo-Code” was set to No in Field Service Settings.
  • Corrected an incorrect Agreement Booking Setup recurrence validation error for “Too many days in month.” Under certain circumstances, this error was thrown inappropriately.
  • Resolved an issue with duplicate section and tab IDs in the Connected Field Service which caused issues when trying to uninstall the solution.
  • Corrected a null reference issue in Connected Field Service when loading the Device Summary control on the IoT Alert form.

8.8.22.57

  • The following Field Service 2020 Wave 1 features in GA and Preview planned are included in this release:
    • Incident type AI-based suggestions (preview)
    • IoT alerts AI-based suggestions (preview)
    • Leverage Power Automate flows (preview)
    • Combined asset capabilities across Dynamics 365 Supply Chain Management and Field Service
    • Integration with Dynamics 365 Supply Chain Management
    • Intune support for Field Service Mobile
    • Next generation schedule board experience (preview)
    • Enhanced work hours calendar for resources
    • Requirement dependency for efficient workflow
    • Resource scheduling dashboard
    • Integrated technician time tracking
    • Technician time-capture precision
  • This release also includes all fixes included in the 8.8.14.328 EA package.
  • Corrected some scenarios where the geo code function was being called when "Auto Geo Code Addresses" was set to no.
  • Corrected scenario where msdyn_payment was null on payment details which was improperly throwing the following error "The payment amount can't be less than total amount applied to invoices."
  • Fixed an issue where price list not changing based on changes to work order's billing account. For organizations experiencing this issue, a fix is made available through the "Advanced Settings" field in the Field Service Settings entity, in an effort to not introduce a potentially disruptive change at this time. Copy the following string into the hidden field:

workorder.pricelist.usefrombillingaccount

  • Resolved an issue where the time-only control misinterpreted daylight savings time for certain timezones.
  • Fixed an issue where form logic was not respecting environment configurations on the Lead entity. Customers can now set fields, like "Company," to be business required and the Field Service form logic will respect the setting.
  • Corrected an issue on Work Order Service where the "Total Amount" was not respecting the "Discount" when used in an editable grid.
  • Removed the validation on Bookable Resource which required each Bookable Resource's name to be unique.
  • Fixed an error on the Quote Booking Product where, under certain circumstances, the system would inaccurately throw the following error, "Enter an amount between $0.00 and $922,337,203,685,477.00."
  • Fixed an issue on Work Order quick create from Account where the Billing Account did not populate, correctly.
  • Improved Customer Asset lookup experience from Work Order Incident to ensure the form respects when organizations define their own default lookup view.
  • Resolved an issue where, in certain timezones, Agreement Booking Setup's Preferred Start Time was not appropriately setting on Agreement Booking Dates' Booking Date and the subsequently auto-created Bookable Resource Booking based on the defined "Preferred Start Time."
  • Fixed a scenario where, if an environment sets the default value of msdyn_linestatus to "Used," Work Order Service creation would fail.
  • Added a null reference check to correct an issue if Work Order Service's "Duration to Bill" was not set.

8.8.12.2

  • Fixed an issue where the "Generate Work Order" button from Advanced Find on Agreement Booking Dates was not displaying and working properly.
  • "Due Date" field value on Invoices generated from Agreement Invoice Date is one day early. For organizations experiencing this issue, a fix is made available through the "Advanced Settings" field in the Field Service Settings entity. Copy the following string into the hidden field:

autogeneration.usetimezone.invoiceduedate=true

  • Resolved a bug on Work Order Service records that have been deactivated throwing an error when being reactivated, "Object Reference Not Set to Instance of an Object."
  • Corrected an unhandled error in geocoding that failed if the address contained an extra comma.
  • For organizations that would prefer that Work Orders generated from Cases open in the same window, this can now be controlled through “Advanced Settings” field in the Field Service Settings entity. Copy the following string into the hidden field if you would prefer Work Orders to open in the same tab in the same window:

casetoworkorderwindowbehavior=0

Note

The “Advanced Settings” field on Field Service Settings is not added to the entity form by default.

8.8.11.19

Available in all regions by April 2020

  • Fixed an issue where Agreement Booking Date generation fails when Agreement is owned by a team.
  • Resolved an issue where Field Service client side logic fails when using contact form while in offline.
  • Resolved PO Product form customization issues where
    • If an organization removed the 'Quantity Received' field from the Purchase Order Product, they would be unable to create a new Purchase Order Product record.
    • Work Order and Warehouse values do not auto-populate if the fields are removed from the form.
  • When using Quick Create form for WO from an Account, fixed an issue where some of the fields that were expected to auto-populate were not being populated.
  • If the map control is removed from the work order form, it cannot be added back. The control has been locked to the form so that it cannot be removed from the form.
  • Issue where the primary incident type record of a deactivated WO could not be deactivated; added a validation check to only allow the Work Order Incident record to be deactivated when Work Order is deactivated.

8.8.14.328 (2020 Wave 1 Early Access)

For more information about early access features, visit the opt-in instructions.

  • Before a Work Order Product or Work Order Service is set to Used, the Total Amount is not calculated.
    • Previously, under some circumstances, a Work Order Service line in Estimated status could have a Total Amount value despite not being set to used. This could result in challenges when looking at the Work Order’s total amount and potential downstream invoice discrepancies.
    • This also required an improvement to the Work Order Product and Work Order Service views to ensure we show both the Estimated Total Amount and the Total Amount so users could understand the value in context of the line’s current status.
  • On the Agreement Booking/Invoice Setup, booking and invoice generation time (respectively) could be incorrect if the user who own's the agreement is in a time zone +1 or higher from UTC.
    • Going forward, the system will consider the Agreement Booking/Invoice Setup owner’s time zone when generating date records.
    • This will now mean that Agreement Booking Date and Agreement Invoice Dates will be generated correctly and consistently, relative to the owner’s time zone.
    • Note: Be sure to validate that all existing Agreement Booking Setups and Agreement Invoice Setups owned by users +1 or greater than UTC are correctly configured to generate Invoices and Work Orders per organizational expectations.
  • On Tax Codes, when 'Act As Tax Group' is set to Yes, Tax Rate % and Items Taxable should be hidden.
    • When a Tax Code is configured to act as a tax group, the tax rate and items taxable should be hidden from the user as these values come from the applicable related Tax Code Details for a tax group.
    • Further, on the Tax Code, when the “Act as Tax Group” flag is set to Yes, a form notification will now show on the form to highlight that Tax Code Details must be created for taxes to be applied when the Tax Code is used.
  • On the Opportunity entity’s main Form, Account shouldn't be mandatory if Order Type is not Service-Maintenance Based.
    • When creating an Opportunity, the Account field should only be mandatory if the Order Type is “Service-Maintenance Based.”
  • On the Agreement Booking/Invoice Setup, if a user’s time zone was set to a GMT +1 or higher, the default range of recurrence was auto-calculated to one day before Agreement Start/End.
    • When defining an Agreement Booking/Invoice Setup as a user in a time zone +1 or higher from UTC, then the range of recurrence on the record’s recurrence string was always calculated one day before the start/end date of the related Agreement’s start/end date.
    • This will now calculate the default recurrence range appropriately based on the user creating the record’s time zone.
  • Deprecated Quote Booking Setup’s Margin tab and calculation logic
    • Formerly, on the Quote Booking Setup form, there was a tab that attempted to calculate the margin of the proposed booking setup.
    • Under certain circumstances, this margin calculation could be incorrect.
    • Due to the limited usage of the feature and the complexity involved in supporting every permutation of possible configuration with corrected calculations, the tab and related calculation logic was removed.
  • Introduced better validation messaging if a user tries to increase the quantity on a Quote Line for Service-Based lines.
  • Prevent Agreement Booking Service Task from being saved when Task Type lookup field is null.
    • If an organization customized the Agreement Booking Service Task entity to make the Task Type optional, this would result in downstream errors when trying to generate Work Order Service Tasks.
    • As such, a synchronous plugin was registered that will prevent the creation of an Agreement Booking Service Task if Task Type is null.
  • Fixed typo in error message when Incident Type Requirement Groups is related to an empty Requirement Group Template.
  • Prevent Work Order Service from being saved when the Service lookup field is null.
    • If an organization customized the Work Order Service entity to make the Service optional, this could result in downstream errors.
    • As such, a synchronous plugin was registered that will prevent the creation of a Work Order Service if Service is null.
  • Improved the warning notification message on the "Geo Code Address” button when Bing maps is disabled.

8.8.10.44

Available in all regions

  • Agreement Booking Service Task's Name is overwritten when the related task type changes.
  • Cannot complete booking that has travel time if the Travel Charge Type on the related Work Order's Account is null.

8.8.9.84

  • Script error when Account field is removed from the Opportunity Quick Create form.
  • On create of Account record based on Postal Code functionality, Service Territory is repeated auto-populated, even after the customer removes the initial auto-populated value.
  • Consistency issue in Field Service's Solution Health Hub rule naming when referring to SDK Message Processing Steps.

8.8.8.135

  • Work Order plugin error for SLA KPI Instance.

8.8.8.50

  • Improve error messages when the user attempting an action is missing "Field Service Setting" read privilege.
  • Form logic always turns Incident Type to not required based on Work Order Type, regardless of field settings.
  • Bookings are not shared consistently to all resources on multi-booking Work Orders.
  • Deleting and recreating a Booking associated with a Work Order changes the shared users of Booking.
  • TypeError: Cannot read property 'getDefaultView' when Requested by Contact field removed from RMA form.
  • Agreement Invoice Product Currency Set to Base Currency - should be set to Agreement's Pricelist Currency.
  • See this blog post for more information.

8.8.7.47

  • Removal of Territory from Work Order is not removed from non-primary related requirements.
  • Inappropriate command buttons shown for Opportunity, Quote, and Order Product and Service-based Lines Sub Grids.
  • Field Service Resource privilege exception on create and save of Time Off Request.

8.8.3.533

Read a blog post about this update.

8.8.2.160

Read a blog post about this update.

8.8.1.45

Read a blog post about this update.

8.8.0.88

Read a blog post about this update.

8.7.0.105

Read a blog post about this update.

8.6.0.274

Read a blog post about this update.

8.5.0.345

Read a blog post about this update.

8.4.0.338

Read a blog post about this update.

8.3.0.255

Read a blog post about this update.

8.2.0.286

Read a blog post about this update.

8.8.2.160

Read a blog post about this update.

Field Service On-Premise

Version Status Details
7.x Latest available Link
6.x Not supported

Important notes

Field Service Online End-of-Life for v7.x and earlier

Version history notes for v7.x

Online versions of Field Service v7 and earlier are end of life and no longer supported. Any support requests you submit for these versions of FS, will not be serviced by Microsoft until you upgrade to the latest version.

Please upgrade legacy versions of Field Service directly from the admin center.

This is a significant upgrade which has a number of potentially disruptive changes including data model, mobile, and interface changes. Please review the Field Service playbook for more information. Prior to applying the upgrade to production, please first test the upgrade on a non-critical, production-like environment.

All customers are strongly advised to upgrade all legacy versions of FS and PSA to the latest solution versions, immediately.

See also