Sign up to free trial of Dynamics 365 for Field Service
Field service app can be installed from App market.
The licences must be activated by filing in a form. More info here:
Purchased licences can be spread across instances. For example, if 100 bought, then 50 can be used for Production and 50 for Sandbox. Can not use 100 for Production and 100 for Sandbox.
It is useful to populate Field Service with some sample data for demo and training purposes. Please follow this link to populate data and carry out initial configuration
NOTE: Installing sample data package will set up system defaults as required. However it is good to understand configuration.
Enable location / map and Entity scheduling. Any entity in the system can be scheduled including custom entities.
In new UCI environment this can be accessed from bottom left
Figure 1: Resource Scheduling Menu in UCI
Go to Resource Scheduling -> Administration -> Scheduling Parameters
Any entity in the system can be scheduled including custom entities.
Go to Resource Scheduling -> Administration -> Enable Resource Scheduling for Entities
In new UCI environment this is accessed from menu in bottom left
Go to Field Service Settings -> Field Service Settings
Best to go through instructions on Microsoft site. Lot to cover
Pre-defined Security profiles providing access to certain data on forms are available. It is recommended after assigning a security role such as ‘Field Service Dispatcher’, associated Field Security Profile shall also be assigned to user.
Go to Field Service Settings -> Field Service Settings as shown in Figure 2: Field Service Settings in UC above.
Detailed information of all settings available here:
A work order in Dynamics 365 for Field Service has information on what work needs to be done. It is used to coordinate and schedule resources and activities. It can be used for different types of work, such as installations, repairs, or preventive maintenance.
A work order is usually created from a case or opportunity. It is then scheduled either manually or using the schedule assistant and then dispatched. Once the work is complete, it is reviewed and approved by a manager.
- Work order creation: A work order is created, usually from a case or opportunity
- Schedule: The work order is then scheduled.
- Dispatch: The work order is dispatched.
- Service: The work order is performed and details are updated.
- Review/Approval: The work order is reviewed and approved by a supervisor.
- Invoice and inventory adjustment: Inventory adjustments are made and an invoice is generated for the corresponding account.
Work orders can be categorised for reporting etc. Dynamics 365 provides ability to create Work Order Types for segregation. Work Order Type can be installation, sales, repair etc.
In UCD Work Order Type can be accessed by going to
Field Service Settings -> Work Order Type
Please refer to Figure 2: Field Service Settings in UCD
This section illustrates the configuration items that should be aimed set up during workshops. Understanding of following entities will aid in carrying out workshops and justifying the need to gather information around these.
Defining these will assist in reporting and kind of work carried out. For example, installation, repair etc
It is good to have these defined. Work orders can be auto populated by selecting an appropriated Incident Type. These work as a template for Work Orders
This defines the products or services that can be billed to customers. Field Service tab under Product can be used set this as Service or Inventory when adding a product to Work Order.
Only products defined as Service can be selected as Service when creating a Work Order.
Items defined here can be linked to Price List and priced for billing purposes.
These define steps that are needed to complete a Work Order or a Service sold to customer within a Work Order. Service Task Types have estimated duration associated with them. These roll up to calculate duration of Work Order.
It is useful have this set up. This is used when converting Cases to Work Orders.
Dynamics 365 allows for a case to be converted to Work Order automatically. However, there are prerequisites that should be in place for this to happen.
Incident Types, Work Order Types, Services, Tax Code and Price Lists shall be set up for conversion to work.
This should be specified for following entities for conversion to work:
This should be specified on following entities:
- Work Order Type
These should be set up. Incident Type is specified in Case for conversion to work.
These should be set up to be used in Incident Types and Work Orders
Resources can be of various types.
Resource that is not part of your organisation. Subcontract out to these.
Member of the organisation
Any equipment that can be used as resource.
It can be thought of as a Repair centre. Any Repair/ services can take place here. A shop.
Any collection of resources. Two or more workers or group
Resource Categories can be created such as technician, electrician etc. To group, filter and report on resources.
Characteristics of a resource can be defined. Certificates, qualifications, colours etc. These can be match against work order bookings if particular characteristics are required from the booking.
Resource Pay Type keep track of cost of resources being used. When a booking is set to ‘Complete’, journal entry is created according to Pay Type.
Following journal types are available:
- Working Hours
- Business Closures
Resource Pay Type is created for each journal with percentage override. For example, Resource Pay Type for overtime can be set to 125%. When a resource specifies overtime, the normal resource cost will be increased for that period.
Resources Pay Type is defined under UCI by going to:
Field Service Settings -> Resource Pay Type
There are add-ins available at an extra cost from Microsoft at an additional cost. These are powerful add-ins and it is worth mentioning them
This add-in can be configured to automatically schedule work orders for most appropriate resources. It can be configured to optimise bookings for shortest travel time, available work hours and other constraints.
More information can be found at:
Powerful tool that can feed diagnostic information straight into Dynamics Field Service module. Instead of waiting for breakages or incidents to occur, this add-in uses power of Azure and MS Flow to connect devices to internet. Notifications can be set up for defined criteria.
Notification will automatically be sent using Flow to schedule maintenance or service job etc.
Key benefits of Connected Service are:
- Reduce downtime by connecting to IoT devices to diagnose problems before customers are aware of an issue
- Address issues faster by remotely monitoring devices and keeping customers in the loop
- Device telemetry and service maintenance data helps to make intelligent decisions around dispatching technicians with the right expertise, availability, and proximity to the job
More information on setting up installing and Configuring Connected Field Service can be found at: