Dynamics 365 Field Service version history

Release schedule

When a new version of Dynamics 365 Field Service releases, it becomes available in different geographic regions at different times. Use the table below to see when the next release will become available in the region of your environment.

For information about other updates to Field Service, visit the Dynamics 365 release plans.

Station Region Current version Next version Scheduled date
Station 1 First Release 8.8.72.27 TBD 08/26/2022
Station 2 South America, Canada, India, France, South Africa, Germany, Switzerland, Norway, Korea 8.8.71.41 8.8.72.27 08/19/2022
Station 3 United Arab Emirates, Japan, Asia Pacific, Great Britain, Oceania 8.8.71.41 8.8.72.27 08/26/2022
USG 8.8.71.41 8.8.72.27 08/19/2022
Station 4 Europe 8.8.70.26 8.8.71.41 08/19/2022
Station 5 North America 8.8.69.53 8.8.70.26 08/19/2022
Station 6 Goverment Community Cloud, DoD , China 8.8.70.26 8.8.71.41 08/24/2022
Dedicated Scale Groups 8.8.69.53 8.8.70.26 08/19/2022

Note

  • Dates in all regions except Government Community Cloud (GCC), USG, and China indicate the timing of the next automatic update. Dates in GCC, USG, and China indicate version availability; at this time, there is no automatic update for the GCC, USG, and China regions.
  • For all other regions, while most updates should be complete on the scheduled night, updates requiring more time may be completed during dark hours over the weekend indicated in the Scheduled date column.

8.8.75.59 (2022 Wave 2 early access, update1)

This release is an update to Field Service 2022 Wave 2 early access version 8.8.75.36.

(Includes Universal Resource Scheduling version 3.12.87.3).

8.8.72.27

(Includes Universal Resource Scheduling version 3.12.83.6).

8.8.75.36 (2022 Wave 2 early access)

(Includes Universal Resource Scheduling version 3.12.86.7).

The release is only applied when an environment is opted into Early Access and introduces the Field Service 2022 Wave 2 new and updated features as outlined in the release notes.

In addition, this release also includes the following changes:

  • Fixed a bug where estimated duration was not set on work order services created from agreements.
  • Fixed a bug where resource pay type was not reflected in actuals when Time Cost Actuals Source is set to 'Work Order Time Entry Approval'.

8.8.71.41

(Includes Universal Resource Scheduling version 3.12.82.14).

8.8.70.26

(Includes Universal Resource Scheduling version 3.12.81.3).

  • Fixed a bug preventing changes to currency exchange rates to be reflected in work order products.
  • Fixed a bug where inactive asset and functional location records showed in the asset tree view.
  • Fixed a bug that allowed service tasks with an inspection to get marked completed when missing responses to mandatory questions.
  • Field Service (D365) mobile: Added ability to set an Inspection response as read only when a Work Order Service Task is in an inactive state.

8.8.69.53

(Includes Universal Resource Scheduling version 3.12.80.9).

8.8.68.25

(Includes Universal Resource Scheduling version 3.12.79.16).

  • Field Service (D365) Mobile: Improved accessibility of Booking Status control with Talkback and VoiceOver enabled.
  • Field Service (D365) Mobile Bug Fix: Inspections File Picker will open correctly on the Windows application.
  • Field Service (D365) Mobile: While using the application in online mode, the Product View Control will validate inventory and prompt with an error if trying to use a Product which does not have quantity available. Note this prompt may be a confirmation depending on status of Use of product out of Stock setting.
  • Add a condition to workflow (GenerateGeofenceWhenBookingIsCreated) to check that the Booking has a Work Order to avoid making unnecessary plugin calls.

8.8.67.16

(Includes Universal Resource Scheduling version 3.12.78.23).

  • Fixed a bug where screen readers were reading "Default value" text boxes as "Question edit" in inspections.

8.8.66.27

(Includes Universal Resource Scheduling version 3.12.77.18).

  • Fixed a bug that prevented the assets and locations tab from being hidden via customization.

8.8.65.10

(Includes Universal Resource Scheduling version 3.12.76.1).

  • Field Service (Dynamics 365) mobile offline: Fixed a bug where under some conditions, when multiple bookings are assigned to a work order, the resource would not be able to complete service tasks.

8.8.64.13

(Includes Universal Resource Scheduling version 3.12.75.2).

  • Fixed a bug that prevented bookings from being generated via agreement booking setups when the agreement is assigned to "SYSTEM" user.
  • Fixed a bug that prevented the checkbox question from focusing properly in the designer when navigating via keyboard.
  • Fixed a SurveyControl bug that prevented the inspection template form from being saved with no columns.
  • Fixed a bug that prevented deserialization of inspection responses during translation.
  • The "Check if forms have unhealthy customizations" rule now provides better warning messages, and will provide an in-app notification by default.

8.8.63.22

This release is a hotfix on Field Service version 8.8.63.20.

  • Fixed a bug where opening the audit history on a work order would fail and show an error.

8.8.63.20

(Includes Universal Resource Scheduling version 3.12.74.1).

  • Field Service (Dynamics 365) mobile app will now leverage native mobile device controls when inputting date and time.
  • Field Service (Dynamics 365) mobile app will now display optimized mobile keyboards when interacting with fields of specific input type: numeric, decimal, telephone, email, and URL.
  • Field Service (Dynamics 365) mobile app timeline control will now support uploading files from the mobile device in addition to photos.
  • Field Service (Dynamics 365) mobile app will no longer show "Start Task Flow" within global commands by default.
  • Field Service (Dynamics 365) mobile Windows app will now include map view within the booking calendar control.
  • The Customer tab of the mobile bookable resource booking form will include a phone number field for the primary contact of the work order service account.
  • The Customer tab of the mobile bookable resource booking form will support an optional third row of text for street address.

8.8.62.26

(Includes Universal Resource Scheduling version 3.12.73.25).

  • Field Service (Dynamics 365) mobile app: Fixed a bug so booking calendar control will no longer jump to incorrect date when scrolling through bookings on iOS.
  • Field Service (Dynamics 365) mobile app: Enabled the agenda view on the booking calendar control for tablets and Windows devices.
  • Field Service (Dynamics 365) mobile app: Added customer phone number field to the out-of-the-box customer details tab on the bookable resource booking and work order forms.
  • Updated privacy messages on landing page for Bing Maps.

8.8.61.21

This release is a hotfix on Field Service version 8.8.61.14.

  • Field Service (Dynamics 365) mobile app: Fixed a bug so booking calendar control will no longer jump to incorrect date when scrolling through bookings on iOS.

8.8.61.14

(Includes Universal Resource Scheduling version 3.12.72.9).

  • Fixed a bug where a work order’s price list, set from a service account, is cleared when changing work order type.
  • Fixed a bug where the price list lookup on agreement invoice product form was showing units instead of price lists.
  • Fixed a bug where service durations were rounded up when converting opportunities to work orders.

8.8.60.21

This release is a hotfix on Field Service version 8.8.60.18.

(Includes Universal Resource Scheduling version 3.12.71.20).

8.8.60.18

(Includes Universal Resource Scheduling version 3.12.71.16).

  • Field Service (Dynamics 365) mobile will correctly show times adjusted for daylight saving time on the booking calendar control.
  • Field Service admins will see a notification within Dynamics 365 Field Service if their organization is using Field Service Mobile (Xamarin app). This notification will inform users of the upcoming end-of-Life timeline for Field Service Mobile (Xamarin app).
  • Fixed a bug in the Field Service (Dynamics 365) mobile app to prevent an intermittent error from displaying after selecting a push notification.

8.8.59.26

This release is a hotfix on Field Service version 8.8.59.22.

  • Fixed a bug in Field Service (Dynamics 365) mobile to correctly adjust times shown in the booking calendar control for daylight saving time.

8.8.59.22

(Includes Universal Resource Scheduling version 3.12.70.3).

  • Fixed a bug in Field Service (Dynamics 365) mobile where quick notes component will now respect maximum character length as defined in msdyn_text.

8.8.58.9

(Includes Universal Resource Scheduling version 3.12.69.1).

  • Fixed bug: Estimated duration in the incident was incorrectly recalculated to zero even if it was originally set to one hour when work order service tasks with estimated duration of zero are deleted.
  • Fixed bug: In the Field Service (Dynamics 365) mobile app, introduced a fix to prevent the booking calendar control from jumping or jittering when scrolling through bookings.

8.8.57.19

(Includes Universal Resource Scheduling version 3.12.68.8).

  • Fixed bug: Date Window Start and Date Window End fields are not visible when field service settings are updated to show.
  • Fixed bug: Customer can't set Auto Generate Work Order to No with the agreement business process flow.
  • Fixed bug: Case field Description was not copied to work order instructions fields.
  • Fixed bug: Field Service (Dynamics 365) mobile--under some circumstances, navigating back from a booking to the booking calendar would display previous month instead of current month.

8.8.56.23

(Includes Universal Resource Scheduling version 3.12.67.1 ( Includes Resource Scheduling controls version 1.2.8.213282 )).

  • Field Service mobile: Input fields on the Bookable Resource Booking – Service form component will now be positioned below the field label, improving readability by allowing the field to fill the horizontal width of the form.

8.8.55.10

(Includes Universal Resource Scheduling version 3.12.67.1 ( Includes Resource Scheduling controls version 1.2.7.213012 ))

  • FS sample data is failing to install due to old version of Package Deployer. Current work around is to request trial from Field Service | Microsoft Dynamics 365 which has sample data.
  • Bug fix for Work Order estimate SubTotal and Estimate Total Amount not considering the Unit of the product.

8.8.54.21

(Includes Universal Resource Scheduling version 3.12.66.3).

  • Fixed issue where updating work order product failed for users with limited privileges to the parent work order record.
  • Updated the Field Service dispatcher and resource security roles to have the read privileges of BookingSetupMetadata set to organization.

8.8.53.36

This release is a hotfix on Field Service version 8.8.53.27.

8.8.53.27

(Includes Universal Resource Scheduling version 3.12.65.6).

  • Bug fix to address "Please wait" message not closing for Convert to WO on case form.
  • Fixed a bug in Field Service (Dynamics 365) mobile to reset travel calculation variables after successful save.

8.8.52.127

This release is a hotfix on Field Service version 8.8.52.125.

(Includes Universal Resource Scheduling version 3.12.64.78).

8.8.52.125

This release is a hotfix on Field Service version 8.8.52.123.

  • Bug fix where instructions field clears on work order save.

8.8.52.123

This release is a hotfix on Field Service version 8.8.52.121.

  • Fixed bug causing issue loading preview of an inspection template in certain scenarios.

8.8.52.121 (2021 Wave 2 release)

(Includes Universal Resource Scheduling version 3.12.64.46).

  • Added a product deletion validation with dialog when the product is associated with purchase orders that must be deleted before the product can be deleted.
  • Better save experience on booking dialog to address save being blocked by pending booking status validations.
  • Fix bug where the Export Selected Records command was not available when multiple items were selected in the work order list view.
  • Knowledge articles ("Linked Articles") sub-grid has been moved below Resolutions sub-grid on the bookable resource booking services tab in the Field Service (Dynamics 365) mobile app.

8.8.51.168 (2021 Wave 2 early access, update 2)

This release is an update to Field Service 2021 Wave 2 early access version 8.8.51.114.

(Includes Universal Resource Scheduling version 3.12.62.63).

  • When there is only one price list per currency on the billing account, we apply that price list to new agreements, work orders, and return merchandise authorizations (RMA).
  • Added a tax code quick create form.
  • Fixed issue where estimate duration field on work order incident form isn’t updated correctly when deleting or deactivating child service tasks.
  • Added field Field Service Product Type to the product quick create form used in the Field Service (Dynamics 365) mobile app.

8.8.50.13

(Includes Universal Resource Scheduling version 3.12.52.4).

  • Fixed a bug in Field Service (Dynamics 365) mobile app where bookings were not always showing in agenda or day view when accessing from work order.
  • Fixed a bug where an error was shown while trying to add a "used" work order product in Field Service (Dynamics 365) mobile app while offline.
  • Added new entries in Solution Hub to help flag configuration issues with Field (Dynamics 365) Service mobile app.
  • Improved the Field Service Solution health rules related to agreements to exclude inactive records from evaluation.

8.8.49.21

(Includes Universal Resource Scheduling version 3.12.51.1).

  • Corrected an issue where inactive service tasks could still be created as work order service tasks when generating a work order from an agreement booking setup that had an incident type referencing the inactive service task type.
  • Resolved a potential null reference error related to work order service tasks that do not have a value in the inspection lookup, which could block the creation of the work order service task.
  • Fixed an issue with potentially inconsistent values in the Total Amount field of a work order service.
  • Improved unclear error messaging on work orders.
  • Resolved an issue where, if a work order product or work order service was reparented between work orders, the impacted work orders' Estimated Subtotal Amount was not accurately recalculated.

8.8.51.114 (2021 Wave 2 early access, update 1)

This release is an update to Field Service 2021 Wave 2 early access version 8.8.51.75.

(Includes Universal Resource Scheduling version 3.12.61.21).

  • Improved the logic that updates the Instructions field on the work order when the service account is updated.
  • Field Service (Dynamics 365) mobile calendar will show a text informing when a booking is scheduled without work order assigned.

8.8.48.30

This release is a hotfix on Field Service version 8.8.48.23.

  • Fixed script error on quick create opportunity form.

8.8.48.23

(Includes Universal Resource Scheduling version 3.12.50.27).

  • Resolved a permissions inheritance issue that could impact users who have a role which worked when users belonged to a team with the same role.
  • Fixed an issue related to decimal point number formatting with inspections when using a symbol other than the dot to indicate the decimal place.
  • Field Service (Dynamics 365) mobile added the ability to configure custom fields on the mobile booking calendar control.

8.8.51.75 (2021 Wave 2 early access)

(Includes Universal Resource Scheduling version 3.12.49.18).

The release is only applied when an environment is opted into Early Access and introduces the Field Service 2021 Wave 2 new and updated features as outlined in the release notes.

In addition, this release also includes the following changes:

  • Multi-line text fields in the Field Service (Dynamics 365) mobile app forms will dynamically expand in height to show all content within the field.
  • Metadata including image and description is added for Field Service (Dynamics 365) mobile controls.
  • Work order in the Field Service (Dynamics 365) mobile app will default to use modern task-completion controls for WOS, WOP, and WOST.
  • Minor text-casing changes within tabs of the Field Service (Dynamics 365) Product form.
  • Improved views for Incident Type Product, Incident Type Service, and Incident Type Service Task.
  • Improved views for Work Order Incident.
  • Move Product Inventory to the top of the "Inventory" area within the Field Service app.
  • Improved error handling on certain crew related booking scenarios.
  • Added plugin validation to enforce that "Product" is required for a work order product.
  • Added plugin validation to enforce that "Service" is required for a work order service.
  • Corrected an issue where, when updating the currency on an existing work order, the Estimated Subtotal Amount currency wasn't accurately reflecting the update.
  • Resolved an issue on order lines in custom apps which could cause the order field not to be populated as expected if the app contained certain customizations.
  • Improved tab naming on the Booking Journal entity.
  • When deleting or deactivating the last work order service task on a work order incident with duration, the duration of the work order incident updates, appropriately.
  • Made keyboard and usability improvements to the Assets and Locations control.
  • Resolved an issue where, when cycling a work order product from estimated to used and back multiple times could leave a previous value in unit amount which should have been nullified.

8.8.47.21

(Includes Universal Resource Scheduling version 3.12.49.18).

  • Resolved an issue where the user-provided Pricelist value on a work order could be cleared under certain form customization scenarios.
  • Corrected a validation issue on work order incidents which was causing users to be blocked from being able to update the work order incident's duration even when there were no work order service tasks on the record which carried a duration.
  • Improved error handling on work order service task creation to provide a more specific error under certain circumstances.

8.8.46.28

This release is a hotfix on Field Service version 8.8.46.26.

  • Reverted an internal code change to avoid potential performance impact.

8.8.46.26

(Includes Universal Resource Scheduling version 3.12.49.18).

  • Update Field Service booking form logic to automatically update Actual Arrival Time on update of Start Time if the pre-change values of Start Time and Actual Arrival Time were the same.
  • When creating a follow-up work order from Field Service (Dynamics 365) mobile, there will be a link created between the source and new work order.
  • Field Service (Dynamics 365) mobile calendar control will now show date and time format based on personalized settings.
  • Fixed an issue where booking status was showing "undefined" in mobile map control.
  • Corrected an issue where, when a work order product was moved from one work order to another, the respective work orders' Estimated Subtotal Amount values were not being recalculated.
  • Resolved an issue with purchase order product records that kept the Product field active and editable even when the record's status was inactive.
  • Fixed an issue with Enhanced Background Processing on agreements where an object reference error could occur when updating agreement invoice setup records if the workflow is deactivated.
  • Added Field Service health improvements including rule enhancements and new rules.
  • Applied performance improvements.

8.8.45.47

This release is a hotfix on Field Service version 8.8.45.47.

  • Reverted an incorrect validation on work order incident which caused the Estimated Duration field for the work order incident to be read-only if the work order incident contained work order service task records, even if those work order service task records did not have a defined estimated duration.

8.8.45.45

This release is a hotfix on Field Service version 8.8.45.35.

  • Fixed an issue that could cause an error when the legacy address suggestion control was used on custom forms.
  • Reverted a previous performance change which under certain circumstances could cause an error to occur.

8.8.45.35

(Includes Universal Resource Scheduling version 3.12.48.25).

  • Created an Advanced Settings flag for bookingjournal.durationcalculationwithoutseconds.optin=true/false which, when true, ensures that booking journal duration is calculated without seconds to resolve potential visual discrepancies due to the number of seconds between milestone events.
  • Resolved a script error message related to opening the agreement's main form.
  • Fixed an incorrect crew booking cascade behavior after an initial crew's bookings were canceled and subsequently rescheduled with a new set of bookings.
  • Resolved an issue with share/unshare logic on work orders with multiple bookings to multiple user resources.
  • Corrected a localization issue with time formatting in the Field Service mobile agenda and map controls.
  • Reverted a previous performance change which under certain circumstances could cause an error to occur.
  • Improved Field Service health rule "Process deinitions in draft status."
  • Updated the validation for booking's End Time and Actual Arrival Time to allow them to have equal values.
  • Updated booking logic to automatically update Actual Arrival Time if Start Time is updated and Actual Arrival Time is not updated and where the pre-change Start Time is the same as pre-change Actual Arrival Time.
  • Improved cascading logic for crew bookings to reduce the possibility of data discrepancies and related, downstream errors on shared booking fields, depending on the crew's defined strategy.
  • Improved logic which populated the Actual Arrival Time to populate the value without seconds which were not visible to the end user and which increased the potential for validation errors which would be potentially incorrect and unobvious to resolve.
  • Fixed an issue where, if customers created agreement booking dates manually after the agreement booking setup create the initial set of agreement booking dates and retriggering the agreement booking setup to create agreement booking dates for an earlier, still-future time range, the agreement would not generate booking dates for the new time range prior to the manually created agreement booking dates.
  • Added Generate Actuals toggle to Field Service settings which will allow organizations to disable actuals generation in Field Service. Additionally, when disabled, the time entry cost actuals generation field in Field Service settings is hidden since this setting becomes irrelevant.
  • Improved Field Service health with additional rules.
  • Applied performance improvements.

8.8.44.56

This release is a hotfix on Field Service version 8.8.44.52.

  • Reverted an incorrect validation on work order incident that caused the Estimated Duration field for the work order incident to be read-only if the work order incident contained work order service task records, even if those work order service task records did not have a defined estimated duration.

8.8.44.52

This release is a hotfix on Field Service version 8.8.44.50.

  • Fixed an issue that could cause an error when the legacy address suggestion control was used on custom forms.

8.8.44.50

(Includes Universal Resource Scheduling version 3.12.47.108).

This release is a hotfix on Field Service version 8.8.44.45.

  • Reverted a previous performance change that under certain circumstances could cause an error to occur.

8.8.44.45

(Includes Universal Resource Scheduling version 3.12.47.98).

This release is a hotfix on Field Service version 8.8.44.39.

  • Fixed a permissions issue with the Field Service dispatcher role that could cause an error to be thrown when dragging an onsite requirement onto the schedule board when "Auto Update Booking Travel" is enabled.

8.8.44.39

(Includes Universal Resource Scheduling version 3.12.47.62).

  • Fixed an issue in the new mobile app faced with chart creation for bookable resource booking in customization settings.
  • Fixed an issue with changing pricing fields.
  • Fixed an issue where default view for customer asset lookup field on work order service task form could not be changed.
  • Fixed an error in Field Service upgrade with the error saying that the element "tab" has incomplete content. -Fixed an issue with subgrids on work order form opening main form instead of quick create form.
  • Removed an issue in agreement booking where the default system status was getting automatically updated to a different value.

8.8.43.101

This release is a hotfix on Field Service version 8.8.43.97.

  • Reverted a previous performance change that under certain circumstances could cause an error to occur.

8.8.43.97

(Includes Universal Resource Scheduling version 3.12.46.64).

This release is a hotfix on Field Service version 8.8.43.93.

  • Sometimes, you might not want a booking start time to be set to current time when the booking status is set to "on site". A new setting has been added to Field Service advanced settings to address this. On adding bookableresourcebooking.disablefsmtravelingcaluclations set to true to the advanced settings, booking start time would not be set to current time.

8.8.43.93

This release is a hotfix on Field Service version 8.8.43.77.

  • Fixed a bug that removed the work hours tab from the resource form.

8.8.43.77

This release is a hotfix on Field Service version 8.8.43.51.

  • Fixed some performance issues.

8.8.43.51

(Includes Universal Resource Scheduling version 3.12.46.21)

  • Fixed an issue where work order product, work order service, or work order service task were getting created for inactive incident type product, service ask and service task respectively through agreements.
  • Fixed an issue for invoices auto generated from work order that invoice date is sometimes updated to one day more or less than the actual date. A new advanced setting Workorder.InvoiceDate.InUserTimeZone=true has been added, which can be set to fix the issue.
  • Corrected an issue in the case a custom real-time workflow is specified on work order after create to update any of the primary requirement fields. For example, priority where the requirement failed to reflect the changes.
  • Fixed an issue where time-off request gets created incorrectly when the record is created from the portal and also incorrectly reflects in the schedule board.

8.8.42.66

(Includes Universal Resource Scheduling version 3.12.45.28).

Includes all content from Field Service version 8.8.42.64.

8.8.42.64

This release is a hotfix on Field Service version 8.8.42.55.

  • Fixed some performance issues.
  • Fixed a bug that removed the work hours tab from the resource form.

8.8.42.55

This release is a hotfix on Field Service version 8.8.42.31.

  • Fixed an issue in Field Service – Dynamics 365 mobile app where end time would be improperly set and cause unexpected time validation errors.

8.8.42.31

(Includes Universal Resource Scheduling version 3.12.45.7)

  • Frontline workers can view bookings in a map view as well in the new mobile app.
  • Fixed an accessibility issue with assets where the More button shown as triple dots was getting skipped from tabbing.
  • Corrected an issue of OnSave event handlers being removed from case form on Field Service installation.
  • Corrected behavior to not throw an error when the field address1_line1 is not present in the form.

8.8.41.58

This release is a hotfix on Field Service version 8.8.41.53.

  • Fixed an issue in Field Service – Dynamics 365 mobile app where end time would be improperly set and cause unexpected time validation errors.

8.8.41.53

This release is a hotfix on Field Service version 8.8.41.28.

  • Added an advanced setting to disable product bundle validation. If user sets product.bundle.optout=true then user would be able to add new or modify existing product bundle with Field Service type set.

8.8.41.28

(Includes Universal Resource Scheduling version 3.12.44.127)

  • Fixed an issue in business process flow being available on a copied agreement.
  • Corrected an issue with work order product where estimate total cost was not getting updated when quantity was changed.
  • Fixed an issue in Field service settings Inspections tab where update of "Analytics enabled" and form save was failing.
  • Updated to throw a form error if the user is trying to create a product bundle and they have set the Field Service Product Type value as product bundles cannot be used with Field Service.
  • Fixed an issue where notes failed to load in the Field Service (Dynamics 365) mobile app when opened in airplane mode.
  • Fixed an issue where upon opening a work order, an error dialog is shown when "Disable Customer asset validation state" is set to Yes under Field Service settings.
  • Fixed an issue to enable users to change line status of work order product from null to some nonnull value without any error.
  • Made performance improvements with system actions invoked during time entry view load.
  • Corrected an issue where quick book triggered from the new work order experience was not respecting work order's territory.
  • Fixed the following issues with inspections:
    • Selecting a date value from the date control automatically updated the date to one day before the selected date.
    • In the exported PDF, the question description was hidden.
    • Entity lookup value getting removed on change of focus.
    • Enhanced support for Hebrew, Arabic, Japanese characters in the imported JSON.
    • Fixed an issue with exported inspection JSON where options in checkbox, radio button, and dropdown questions were getting duplicated.
    • Fixed a performance issue in generating the inspection response pdf.
    • Fixed an issue with inspection load failure in offline with a lot of attachment questions.

8.8.40.141

This release is a hotfix on Field Service version 8.8.40.109.

  • Fixed a Field Service upgrade issue when the relationship between knowledge article and customer asset/product already existed in the active layer.
  • Fixed a Field Service upgrade issue that was throwing error like ‘Property Inspection is required, but the declaration is missing’

8.8.40.109

(Includes Universal Resource Scheduling version 3.12.43.71) This version introduces the Field Service 2021 Wave 1 new and updated features outlined as generally available. It also introduces all of the changes from the early access versions of this release.

This version also introduces the following key capabilities:

  • First-run experience to get started setting up Field Service. This new experience can be seen in the Get Started section in the sitemap.
  • Ability to assign frontline workers with characteristics, territories, and other properties. View or edit the security roles, field security profiles, and mobile offline profiles that are automatically assigned to the frontline worker. Automatically send an email to frontline workers with the link to download the Dynamics 365 Field Service mobile app. Ability to view a list of all your frontline workers and edit their properties on the bookable resource form.
  • Field Service's Bing maps capabilities are enabled by default. This update can also be seen in the Get Started section.
  • Other than the work order form improvements released in early access, more enhancements have been made, including quick-create for work orders and making tax code optional.
  • Question types textbox, radio buttons, checkboxes and dropdowns in inspection templates can now have default values also be set before publish.

Fixes include:

  • Fixed an issue where work order service form could not be loaded properly from subgrid embedded in the custom quick view form of work order when Work Order Subgrid Records Open as Popups was enabled.
  • Corrected an issue in entitlement application regarding slow performance in form library when there are a large number of accounts.
  • Fixed an issue of duplicate agreement booking dates being generated for certain agreement and time zone criteria.

8.8.35.44

This release is a hotfix on Field Service version 8.8.35.27.

  • Resolved an issue where, under certain circumstances, work orders with a primary incident type that also executes a synchronous workflow, could result in null fields on the work order and related primary resource requirement.
  • Reverted the below change: "Updated behavior where estimated duration from agreement booking setup was not carried over to work order. Previously, duration from the resource requirement was not being used to calculate total estimated duration in the work order. This behavior has been updated; if no work order service task or incident is present, total estimated duration is obtained from the Requirement. If requirement duration is null, then we get value from booking setup metadata."

8.8.39.142 (2021 Wave 1 early access update)

This release is a hotfix on Field Service version 8.8.39.135.

  • Fixed a Field Service upgrade issue when the relationship between knowledge article and customer asset or product already existed in the active layer.
  • Fixed a Field Service upgrade issue that was throwing error: "Property Inspection is required, but the declaration is missing."

8.8.39.135 (2021 Wave 1 early access update)

(Includes Universal Resource Scheduling version 3.12.43.71) This version introduces the Field Service 2021 Wave 1 new and updated features outlined as generally available. It also introduces all of the changes from the early access versions of this release.

This version also introduces the following key capabilities:

  • First-run experience to get started setting up Field Service. This new experience can be seen in the Get Started section in the sitemap.
  • Ability to assign frontline workers with characteristics, territories, and other properties. View or edit the security roles, field security profiles, and mobile offline profiles that are automatically assigned to the frontline worker. Automatically send an email to frontline workers with the link to download the Dynamics 365 Field Service mobile app. Ability to view a list of all your frontline workers and edit their properties on the bookable resource form.
  • Field Service's Bing maps capabilities are enabled by default. This update can also be seen in the Get Started section.
  • Other than the work order form improvements released in early access, more enhancements have been made, including quick-create for work orders and making tax code optional.
  • Question types textbox, radio buttons, checkboxes and dropdowns in inspection templates can now have default values also be set before publish.

Fixes include:

  • Fixed an issue where work order service form could not be loaded properly from subgrid embedded in the custom quick view form of work order when Work Order Subgrid Records Open as Popups was enabled.
  • Corrected an issue in entitlement application regarding slow performance in form library when there are a large number of accounts.
  • Fixed an issue of duplicate agreement booking dates being generated for certain agreement and time zone criteria.

8.8.39.118 (2021 Wave 1 early access update)

(Includes Universal Resource Scheduling version 3.12.42.5)

The early access update release is only applied when an environment is opted into early access and applies below fixes and changes to the early access release:

  • New note-taking experience in Field Service (Dynamics 365) mobile app allows users to quickly attach text, photo, video, and file notes to bookings.
  • For inspections:
    • New capability to enable an inspection to be added to an asset directly for ad hoc inspection scenarios.
    • New ability to export inspection responses as PDF for a work order service task.
    • Textbox question can now have a read only value along with a default one.
    • New inspection setting added to disable automatic numbering of questions.
    • In matrix (dynamic) control a new setting has been added to allow "Add New" button to be removed.

Additional updates:

  • Fixed an issue with work order service were discount percentage was getting cleared on the form when line status was changed from estimated to used.
  • Corrected an issue to throw an error if an agreement booking incident is created with a customer asset that is not associated to the service account on the corresponding agreement.

8.8.35.27

(Includes Universal Resource Scheduling version 3.12.36.2)

  • Fixed an issue where an error was being thrown when clicking on save and close button after creation of time entry record or clicking on save button and going back to time entry grid.
  • Fixed an issue with agreement booking setup when the currency in product and services was not getting picked up from its associated service account but the base currency in some cases.
  • Fixed an issue in agreement setup wherein the billing account was not getting populated correctly for an agreement when the agreement was being created from an account.
  • Corrected an issue where all the requirements were not being canceled once the work order status was changed to closed - canceled.
  • Inspections "Export to PDF" now includes support for Japanese text.
  • Fixed an issue in work order service task creation with an inspection containing some special characters like '&' in the title.
  • Corrected an issue with inspections containing date time type question where the question no longer remained editable after saving the work order service task and user needed to refresh the page.
  • Fixed an issue for inspections in Arabic language where uploaded file in a file type question was not showing up after form refresh and reopen, and the delete and clear files buttons at the uploaded file were also not working.
  • Corrected an issue where update quantity failed for purchase order receipt product.
  • Fixed an issue of failure in receiving notifications on iPhone in the Power Apps mobile app after scheduling a work order and when geofence record status is changed.
  • Added a new solution health rule to check if the recurrence setting for agreement booking setup is present and is valid.
  • Fixed an issue where the help center page was showing up in English instead of Japanese.
  • Updated behavior where estimated duration from agreement booking setup was not carried over to work order. Previously, duration from the resource requirement was not being used to calculate total estimated duration in the work order. This behavior has been updated; if no work order service task or incident is present, total estimated duration is obtained from the Requirement. If requirement duration is null, then we get value from booking setup metadata.

8.8.39.37 (2021 Wave 1 early access)

(Includes Universal Resource Scheduling version 3.12.40.15)

The release is only applied when an environment is opted into Early Access and introduces the Field Service 2021 Wave 1 new and updated features as outlined below for availability in early access:

  • Work order resolution information capture
  • Improved Field Service usability with major enhancements for the work order form, the account form, and changed a number of other customer-facing behaviors across a number of interaction points within the solution. -Replaced address suggestion experience with the new address control.
  • Embedded knowledge management.
  • For inspections:
    • Multilingual support for an inspection with a new tab 'Translation' in inspection designer.
    • Added filter condition support in entity lookup to reduce the lookup results.
    • Added compact layout option to show more questions in screen.
    • Added dependent entity lookup to improve filtering of results using another question in same inspection.
    • Export an inspection as json and import an inspection json in another environment which is useful for moving long inspections.
    • Rename of 'Inspections' sitemap entry to 'Inspection Templates.'
    • Added a new button to publish an inspection template and create a service task type in one go.
    • Added a new setting to enable online only scenarios to attach files and images larger than the current 3 mb limit. For this a setting has been added to Field Service Settings under the 'Advanced Settings' field as inspection.allowuploadlargefilesonline=false. To enable files more than 3 mb in size to be added when online, false can be changed to true.

In addition, this release also includes the following changes:

  • Tax code has been made optional so that user is not forced to enter data that is not capable of supporting the complexity of the tax scenarios.
  • Recently a new flag for workorderincidentitem.statecodeupdate.optout had been introduced. The dependency on this flag has now been removed. The workorderincident items state code would be updated only when new state code is different from old state code.
  • Fixed and issue with work order product that estimate discount % is cleared on the form when using a decimal.
  • Corrected an error with work order product that discount % is cleared on the form when line status is changed from estimated to used.
  • Fixed an issue of missing details tab in the sales hub order.
  • Corrected a behavior in time entry form that on save end date gets auto populated even if both end date and duration fields are made optional and null.
  • Updated view name 'Purchase Order Lookup View' to 'Purchase Order.'
  • A change has been made with work order incident duration to be read only when it has child service tasks with estimated durations so it matches the total durations of its child service tasks.
  • Fixed an error while saving product and service based lines to quote.
  • Updated the error string to be more descriptive of the issue when trying to save a user, account, contact, or work order if geocode action is disabled.
  • Fixed an error of missing dialog to reparent pop-up in work order service task on adding non related customer asset when customer asset validation state and suggest reparenting customer asset are enabled
  • Optimized sync filters for entities like account, contact, and product to improve performance in model driven mobile app.
  • Improved error message when a knowledge article is opened in offline mode on mobile.
  • Fixed an issue of missing "Assets and Locations" and "Properties" tabs in an asset form.

8.8.34.63

(Includes Universal Resource Scheduling version 3.12.35.6)

Includes all content from Field Service version 8.8.34.18

8.8.34.18

(Includes Universal Resource Scheduling version 3.12.35.5)

  • Fixed an issue regarding register devices command showing up in an asset form even though the environment is not configured to use IoT.
  • Fixed an issue with device ID field getting cleared when the asset form is refreshed.
  • Fixed an issue in response generation after clicking on "Send Command" for an IoT device.
  • Added date time support in inspections matrix control.
  • Fixed an error opening Dynamics 365 Remote Assist if the support contact contains a user in Japanese.
  • Fixed a console error when opening a customer asset quick create form from work order form due to absence of functional location.
  • Corrected an issue in the population of Time To Promised and Time From Promised fields when the work order is created with an SLA.
  • Fixed an issue with taxable while creating agreement from account record type.
  • Fixed an issue in the creation of time entry from a bookable resource booking wherein a resource or work order was not getting populated.
  • Fixed an issue in the Field Service model-driven app regarding icons for some entities not showing up in the sitemap.

8.8.33.99

(Includes Universal Resource Scheduling version 3.12.34.92)

Includes all content from Field Service version 8.8.33.61

8.8.33.98

(Includes Universal Resource Scheduling version 3.12.34.60)

Includes all content from Field Service version 8.8.33.61

8.8.33.61

(Includes Universal Resource Scheduling version 3.12.34.4)

  • Allow technicians using the mobile app to quickly create follow up work orders.
  • Optimize unwanted calls for IoT entities during form loads of work order and case.
  • Corrected an issue with connected IoT device not showing up in connected device subgrid of the asset.
  • Performance improvements in Connected Field Service and IoT asset.
  • Removed deadlock errors on product inventory in the work order generation.
  • Corrected an issue with resource requirement preferences to show up with requirements.
  • Corrected batch size related error in work order sharing and unsharing.
  • Fixed an issue in work order creation when rating value is null for a characteristic associated with agreement booking incident.
  • Corrected privilege errors when trying to save work order and child records if there is no read privilege to Field Service settings.
  • Improved the error handling when work order closure and the unit cost field of work order product is not filled.
  • Fixed the behavior to set custom default view for customer asset lookup control on the agreement booking incident form.
  • Corrected an issue of missing "New" button on time entry form in IE 11.
  • Fixed an error when saving work order resulting from an issue in the deletion of requirement resource preferences.
  • For the error that service tasks get reactivated even when tasks are completed and work order is completed, a new flag workorderincidentitem.statecodeupdate.optout=true can be added in the Field Service settings page in the "Advanced Settings" field, under the "Other" tab. The new flag can be added to any flags already present and delineated by a new line.
  • Corrected an issue in geocode command button not being visible in offline sometimes.
  • Excluded a sales related deprecated web resource.
  • Corrected an issue with service tasks not showing up on mobile while offline.
  • Fixed an issue with add and edit options being hidden for assets and functional locations.
  • Corrected an issue in billing account population when creating a work order from account.
  • Improved the usability of the matrix control in inspections.

8.8.32.61

This release is a hotfix on Field Service version 8.8.32.59

  • Improved error handling when a work order is closed.
  • Fixed a performance issue in IOT caused by a recent change.

8.8.32.59

(Includes Universal Resource Scheduling version 3.12.33.8)

Field Service

  • For inspections:
    • Added the ability to capture photos for the file upload question type in Field Service Mobile.
    • Added barcode scan option to the textbox control.
    • Added a new control called "Matrix (Dynamic)" to the toolbox. Use this control to add a grid of questions to which you can add more rows dynamically while performing the inspection.
    • Increased the maximum character limit for the description of a question to 1000 characters.
    • Improved the "Export as pdf" behavior to include the new grid control and the questions hidden behind branching logic in the PDF generated for an inspection.
    • Added a new field "Depends on" to entity look up to filter lookup options based on response to another entity lookup question.
  • Corrected booking journal duration calculation to be more accurate.
  • Resolved an issue: upon reassigning a booking from a crew type resource to user type resource, the Crew and Crew Member fields would not clear.
  • Improved the behavior of "Generate Agreement Booking Dates" workflow instances to cancel if the parent workflow deactivates.
  • Updated the customer asset quick create form to make it customizable.
  • Improved pricing calculation of a work order product to ensure accuracy regardless of the user’s privileges.
  • Corrected an issue to enable more than 5000 work order products to associate to a work order.
  • Resolved an issue in calculation of Total Amount in work order service when Duration To Bill is 0.
  • Corrected an issue when loading the inspection designer for Italian orgs.
  • Reverted a previous change for an issue: resource preferences wouldn't copy to the non-primary requirements introduced by an incident type requirement group.
  • Corrected an issue: an error for "The given key was not present in the dictionary" error could pop up while saving a priority form.
  • Resolved a false failure issue of Field Service Health rule that checked for web resources.

Field Service mobile app

  • Created new controls for the work order service task, work order product, and work order service subgrids on the booking and work order form in Field Service Mobile. These controls were designed to give mobile technicians a quick and easy way to mark items complete or used and to have at-a-glance visibility into what still remains.
  • Improved mobile offline filter handling for the time-off request table.

8.8.31.60

(Includes Universal Resource Scheduling version 3.12.32.1)

  • Improved error handling and messaging when the work order table is missing a booking setup metadata record. Previously, this scenario would throw a generic object reference error, which didn't help troubleshoot the issue.
  • Enabled viewing related agreement booking incident records from a customer asset. Previously, this relationship was not visible from the customer asset.
  • Improved conversion of an opportunity into a work order. The conversion from opportunity with opportunity products, now maintains the defined opportunity product’s Sequence Number as Line Order in the work order’s work order products.
  • Corrected an issue with the agreement invoice setup’s invoice generation process, which could cause a generic error when the agreement invoice date tried to generate an invoice if the agreement invoice setup contained invoice products.
  • Updated the solution to ensure that multi-resource work orders using requirement groups respect the resource preferences defined on the related service account for all requirements generated against the work order.
  • Resolved an issue in a solution patch that inappropriately removed on-save handlers from the case table.
  • Corrected an issue that caused any update of a work order product record to update the work order product’s Exchange Rate, even if there were no updated currency-related fields, after a change to related currency’s exchange rate value.
  • Enhanced the logic on agreement booking date records that could cause unnecessary background processes to fire causing a momentary block from being able to update the related agreement booking setup. This logic improved to reduce the scenarios under which it would try to trigger this background process, removing scenarios where the agreement booking date’s Booking Date was update to a time further in the future. When this value pushes out further, the background process does not need to be triggered.
  • Improved mobile offline filter handling for the warehouse table.
  • Updated the Field Service Health rule name from “Waiting workflow instances owned by disabled user accounts” to “Waiting workflow instances owned by disabled users.”
  • This release introduces the solution components for the improvements to the Dynamics 365 Supply Chain Management integration as outlined for availability in Wave 2, 2020. These integrations, the metadata, and their required logical changes are only introduced when dual-write is enabled on your environment.

8.8.30.113

This release is a hotfix on Field Service version 8.8.30.103.

  • Resolved an issue with agreement invoice setups introduced during early access that caused an error in the primary invoice date and invoice generation process, which could stop invoice generation from agreements.
  • Corrected a JavaScript error when trying to create a work order through the quick create form.
  • Resolved an issue with inspection name value being empty in the parsed inspection record tables.

8.8.30.103

(Includes Universal Resource Scheduling version 3.12.31.50) This version introduces the Field Service 2020 Wave 2 new and updated features outlined as generally available. It also introduces all of the changes from the early access versions. In addition, it introduces the following updates:

  • Resolved an issue that had the potential to cause timeouts based on resource location updates from Field Service Mobile.
  • Improved update logic to a work order product's currency field to ensure that non-currency related changes did not appear as also making an update to the currency field.
  • Corrected an issue: under certain circumstances, the system could autogenerate duplicate agreement booking date records when updating Auto Generate Work Order.
  • Corrected behavior where it was possible to have the value of Date Window Start reverted on save if a user followed a specific record update pattern and got a form validation.
  • Resolved an issue: if a user provided a name to a work order incident record that was different than the automatically provided value, then deactivated and reactivated the record, the name would revert to the automatic value.
  • Resolved an issue that impacted certain solution update scenarios based on conflicting settings to the CanCreateAttributes attribute in the unit, unit group, and price list item entities.
  • Improved form logic to allow for manual time entry record saving when an org has both Field Service and Project Operations installed.
  • Improved the save/save and close behaviors of a record from within a modal form dialog (MFD) to ensure that the contextual record would automatically refresh so a user can see the immediate impacts of their efforts. An example scenario: a user creates a new booking from a work order, the booking form will now open in an MFD by default. When the user saves and closes the booking form, the contextual work order will refresh. The work order's status will change from "unscheduled" to "scheduled" immediately.
  • Enabled the "Customer Asset Quick Create" and "Asset Work Order Quick View Form" forms to be customizable; initially, they were released as non-customizable.
  • Corrected a problem that could present when bulk editing work order records.

8.8.29.333 (2020 Wave 2 early access update)

(Includes Universal Resource Scheduling version 3.12.30.11)

The release is only applied when an environment is opted into early access and introduces the Field Service 2020 Wave 2 new and updated features.

In addition, this release includes the following changes:

  • Resolved an issue with agreement invoice setups introduced during early access that caused an error in the primary invoice date and invoice generation process that could stop invoice generation from agreements.

8.8.26.24

(Includes Universal Resource Scheduling version 3.12.25.5)

  • Corrected an issue: under certain circumstances, the Discount % in work order product form is automatically cleared on save.
  • Resolved an issue with agreement booking dates: when the booking dates are manually altered, the work orders were not getting auto generated as expected relative to the Generate Work Order Days in Advance value of the related agreement booking setup.
  • Improved handling for the sharing and unsharing behavior of the booking resource booking when the target user is disabled.
  • When exchange rate on a currency is changed, any subsequent changes to a work order service record would result in the exchange rate for that record being updated. It should only be recalculated if a currency-related field is updated.
  • Improved handling of the account’s merge functionality when one of the target accounts has a related Agreement where taxable is "No."
  • Improved handling of the account’s merge functionality when one of the target accounts has a related RMA where taxable is "No."
  • When using tab to navigate away from the Estimate Total Amount field on a work order service record after making an update, the system was inappropriately throwing the error "Enter an amount between $0.00 and $1,000,000,000.00."
  • Corrected a bug: when the work order service’s Line Status was changed from "Estimated" to "Used," the Estimated Discount % field was not getting copied to the Discount %.

8.8.29.226 (2020 Wave 2 early access update)

(Includes Universal Resource Scheduling version 3.12.30.11)

The release is only applied when an environment is opted into early access and introduces the Field Service 2020 Wave 2 new and updated features.

In addition, this release includes the following changes that have the potential to change the existing system behavior or interface:

  • Added quick create forms for all new asset properties-related entities to the Field Service model-driven app.
  • Corrected an issue with a missing space in the "Field Service Activities" tab header for the account entity for the Field Service Mobile model-driven app.
  • Improved the customer asset form to ensure that the IoT related tabs are displayed after the other form tabs.
  • Removed the property logs option from the related menu from the customer asset form.
  • Updated the property log display values to respect user settings for date and time.
  • Corrected travel calculation logic for the Field Service Mobile model-driven app to ensure that, when the booking is set to in progress, if there was no Estimated Travel Duration the system will update the Actual Arrival Time and will not immediately increase total duration.

8.8.29.165 (2020 Wave 2 early access)

(Includes Universal Resource Scheduling version 3.12.29.5)

The release is only applied when an environment is opted into early access and introduces the Field Service 2020 Wave 2 new and updated features as outlined for availability in early access:

  • Embedded Power BI Dashboard for key Field Service metrics
  • Improved work order metrics
  • Asset hierarchy and functional location
  • Usability improvements for key Field Service subgrid as dialogs
  • Enhanced skills-based matching in resource scheduling optimization
  • Predictive technician travel time
  • Travel outside of working hours
  • Enhanced work hours calendar for requirements
  • Connected Field Service on the Dynamics 365 Field Service mobile app
  • Field Service inspections
  • Technician time tracking on Dynamics 365 Field Service mobile app
  • Usability improvements for the field technician booking form
  • Calendar view for booking work orders

In addition, this release includes the following changes that have the potential to change the existing system behavior or interface:

  • Improved logic around agreement booking dates, which have a button to manually “Generate Work Order.” Previously, this button was available when a work order had already been generated. In this release, we improved the logic associated with this button to ensure this button was not available if the work order had already been generated.
  • Corrected the display position of the map control in the “Location” tab for the work orders in the Field Service Mobile app’s default work order form. Previously, the map control appeared between the latitude and longitude fields. It now appears above these fields.
  • When an incident type is applied to a work order, it results in the automatic creation of a work order incident, which can automatically create work order products, work order services, and work order service tasks. These records are associated to the work order and work order incident. If the primary incident customer asset field referenced a customer asset, all resulting records would also be related to the same customer asset. The release improves the logic for customer asset association on these records when a work order incident’s customer asset is updated. Previously, if the customer asset on a work order incident was updated, it would not update the related work order products, work order services, or work order service tasks. It will now update these records appropriately, assuming the customer asset value of the child records matched the pre-change value of the work order incident.
  • Corrected a poor system behavior: when updating a work order service record’s line status from “Estimated” to “Used,” the estimated discount percent value was not autopopulated into the discount percent field. This value will now autopopulate per the estimated value when the line is set to “Used.”
  • Improved the error message on a purchase order receipt product when a user tries to change the quantity or unit after a related purchase order bill has been created.
  • Improved display handling of the agreement and invoice subgrids on the account forms where a user may not have permissions to these related records. Previously, these subgrids would display with an error about the user’s permissions; however, now, these subgrids will not show on the form in such cases of insufficient permissions.
  • Resolved an issue with the Field Service resource role’s permissions. Previously, this role was missing the “Append To” privilege on customer asset, which caused issues when trying to create customer assets.
  • Improved the subgrid name for work order products on the default work order form for the Field Service Mobile app.
  • Fixed an issue where the value for customer asset was not being copied into work order products, work order services, and work order service tasks that were created from agreement booking products, agreement booking services, and agreement booking service tasks that were not related to an agreement booking incident. This association will now flow down, as expected.
  • Added the "Field Service - Resource" role to the new app module for Field Service Mobile.
  • Corrected some consistency issues with the labeling for “Work Hours Templates.”
  • Adding a notification on agreement booking setups and agreement invoice setups to highlight that related work orders, invoices, and dates will not generate when users create or updates the agreement subrecords when the parent agreement’s System Status is not active.
  • Improved work order validation of the latitude and longitude fields to ensure that, if either value is populated, both values are populated, and that the values are valid.
  • Improved warning messages on the booking form. It is not advised to use a work order’s booking through more than one booking lifecycle. It should only go through the lifecycle once (scheduled -> traveling -> in-progress -> complete). Some organizations that reuse a single booking through more than one lifecycle began receiving a form notification that, while allowed, such practices are not advised. This warning previously mentioned time entry generation anytime it was displayed; it will now only mention time entry generation when the environment is configured to autogenerate time entries to avoid confusion.
  • Enhanced logic for work order service task naming if the work order service task was created from a work order incident as a result of the incident type’s incident service task. In such cases, if the incident service task has a name, the work order service task’s name will come from the incident service task; previously, the work order service task’s name was always the name of the related service task type. If the incident service task’s name is blank, the work order service task’s name will default to the service task type’s name.
  • Removed unnecessary code that enforced that the booking and journal type fields on a booking journal would be editable under certain circumstances. These fields will now behave the way the rest of the fields on the booking journal behave.
  • On the case entity, when Field Service is installed, there is a ribbon button to “Convert to WO.” Previously, this button was in an undiscoverable location. This button has been moved to be more discoverable.
  • Improved Field Service Mobile’s user experience for tablet users to ensure proper column width, improved quick create experience, and improved subgrid usability on the booking’s Service tab.
  • Changed behavior on the agreement booking service tasks. Previously, when changing the value of the related task type, the description field would always be cleared. Now it will only be cleared if the new value for task type has an overriding value; otherwise, the value will not be cleared by default.
  • Updated the name for the “My Open Resource Bookings (Field Service Information)” view to simply “Bookings” for optimal use and display in Field Service Mobile.
  • Removed some fields from the default configuration of the booking entity’s default form for the Service tab to improve usability of Field Service Mobile.
  • Replaced the address control used in the Field Service Mobile forms for the account and work order entities with a new control optimized for mobile use.
  • Enhanced the automatic copy logic for related resource preference records onto work orders created for the same account. Previously, when these records were copies, resource preferences of type “Must Choose From” on the account were not being copied to the work order. They will now be copied, as well.
  • Improved usability of the booking’s service tab in Field Service Mobile to show five records in the subgrids, by default, instead of just two, as was the previous behavior.
  • Minor improvement to tax calculation on the work order record to ensure that rounding rules resulted in a consistent value between the work order’s tax calculation and the invoice’s tax calculation. Under certain circumstances, previously, these values could be inconsistent by at the second decimal due to rounding differences.
  • Updated the taxable field in Field Service Mobile forms for work order, work order service, and work order product to use a new toggle control for simplified mobile usability.
  • Improved all default views for work order product, work order service, and work order service task to swap the Product, Service, and Task Type fields respectively with the Name field to improve default view usability.
  • Enhanced validation on the agreement entity when setting the price list to ensure that the currency set on the price list is the same currency set on the related billing account. Previously, this validation was not present, which led to the potential for downstream errors on work order generation since the work order expects currency consistency between these two fields. Now, this validation is present at the agreement, ensuring agreement creation and update will protect downstream operations of the work order.
  • Removed incorrect defaulting logic on creation of work order service, work order product, or work order service task records that were not related to a work order incident. Previously, these records would be associated to the primary incident’s customer asset; however, they will now be left blank by default as they are not necessarily related to the primary incident’s customer asset.

8.8.25.30

(Includes Universal Resource Scheduling version 3.12.24.5)

  • Includes all content from Field Service version 8.8.25.29

8.8.25.29

(Includes Universal Resource Scheduling version 3.12.24.4)

  • Corrected an issue on bookable resource booking forms where the Estimated Arrival Time field can appear as if it has been edited immediately after save (when it hasn’t been), making the form behave as if it had unsaved changes.
  • Improved logic to allow for customizations to the work order form where the primary incident type is removed from the form to ensure that the out-of-the-box form logic has a null check for the Primary Incident Type field.
  • Resolved an issue with missing localization strings on the IoT alert and IoT device entities, which could cause a script error.
  • Fixed an issue on update of agreement booking incident, which produced an error if there was a related agreement booking service task with a null estimated duration.
  • Resolved a problem with the agreement copy function that failed to copy agreements if there were deactivated agreement booking setup or agreement invoice setup records related to the agreement. The copy function will now successfully copy active records and ignore inactive records.
  • Added a new Field Service health rule that will highlight agreement booking setup and agreement invoice setup records on which the latest workflow instance had failed which could keep expected work orders and invoices from being generated. Once detected, the rule also provides a button to resolve failed workflow instances.

8.8.24.54

(Includes Universal Resource Scheduling version 3.12.23.71)

  • Includes all content from Field Service version 8.8.24.17

8.8.24.17

(Includes Universal Resource Scheduling version 3.12.23.26)

  • Corrected a null reference error based on work order product form customizations to better handle when certain fields are removed from the form.
  • Resolved an issue with the incident type duration suggestions feature that produced an error when a user clicked “Recalculate Suggestions” for large query results.
  • Fixed an issue with agreement update, which produced a "Nullable object must have a value" error on updating end date of an agreement whose end date is null.
  • Removed the following BPFs from the Field Service Mobile app module: case to work order, lead to opportunity sales, opportunity sales, phone to case.
  • Improved logic to allow for customizations on work order creation from an agreement if there are customizations in place to automatically create more resource requirement records.
  • Improved Field Service’s missing form libraries rule in Solution Health Hub to improve the rule description.
  • Enhanced logic to in the opportunity quick create form to respect scenarios when an environment sets the “Account” field as business required to ensure that Field Service form logic does not set the field as optional.

8.8.23.85

(Includes Universal Resource Scheduling version 3.12.22.9)

  • 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 that left the status null when created a new geofence, which could cause geofence events to not 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 that 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 Connected Field Service that 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.58

  • Includes release of Dynamics 365 Field Service (Power App), a new mobile app for technicians built on the Power Platform. As part of this release, administrators will see a new app called "Field Service Mobile" in the list of apps.
  • 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)
    • Use 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 called when "Auto Geo Code Addresses" was set to no.
  • Corrected scenario where msdyn_payment was null on payment details; this scenario 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 available through the "Advanced Settings" field in the Field Service settings entity, to not introduce a potentially disruptive change at this time. Copy the following string into the hidden field:

workorder.pricelist.usefrombillingaccount

  • Resolved an issue: 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: the "Total Amount" was not respecting the "Discount" when used in an editable grid.
  • Removed the validation on bookable resource that required each bookable resource's name to be unique.
  • Fixed an error on the quote booking product: 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 the 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 issue: in certain timezones, agreement booking setup's preferred start time was not appropriately setting on agreement booking dates' booking date and the autocreated 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 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 deactivated work order service records throwing an error when 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 action 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 purchase order 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 autopopulate if the fields are removed from the form.
  • When using quick create form for a work order from an account, fixed an issue where some of the fields that were expected to autopopulate 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 work order 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 owns 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 "Yes," tax rate percentage 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 "Act as Tax Group" is "Yes," a form notification will now show on the form to highlight that tax code details are required for taxes to apply when you use the tax code.
  • 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 GMT +1 or higher, it autocalculated the default range of recurrence 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 one day before the start/end date of the related agreement's start/end date.
    • 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, removed the tab and related calculation logic.
  • 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 saving when task type lookup field is null.
    • If an organization customized the agreement booking service task entity to make the task type optional, it resulted in downstream errors when trying to generate work order service tasks.
    • As such, registered a synchronous plugin that will prevent the creation of an agreement booking service task if task type is null.
  • Fixed typo in error message when an incident type requirement group is related to an empty requirement group template.
  • Prevent work order service from saving when the service lookup field is null.
    • If an organization customized the work order service entity to make the service optional, could result in downstream errors.
    • As such, registered a synchronous plugin 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 you disable Bing Maps.

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 you remove account field from the opportunity quick create form.
  • On creation of account record based on postal code functionality, service territory repeats autopopulated, even after the customer removes the initial autopopulated 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 aren't 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 - the currency should set to agreement's price list currency.

8.8.7.47

  • Removal of territory from work order doesn't remove 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.

Field Service On-Premise

Version Status Details
7.x Latest available. Minimum platform version 9.0 for install. 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. Microsoft will not service support requests for these versions of Field Service until you upgrade to the latest version.

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

This upgrade is significant and has many potentially disruptive changes including data model, mobile, and interface changes. Review the Field Service playbook for more information. Prior to applying the upgrade to production, be sure to first test the upgrade on a non-critical, production-like environment.

All customers should upgrade all legacy versions of Field Service and Project Service Automation to the latest solution versions as soon as possible.

See also