Dynamics 365 Field Service : Configure work order types and work order resolutions

In Dynamics 365 Field Service, after setting up your core products and services, the next key configuration is defining Work Order Types and Work Order Resolutions. These settings help streamline scheduling, pricing, and service reporting.

1. Work Order Types

Work Order Types allow organizations to categorize the kinds of service work being performed. Examples include:

  •  Installation
  •  Preventive Maintenance
  •  Inspection
  •  Repair
  •  Standard Service Calls

These categories help automate certain aspects of the work order, such as assigning specific incident types or price lists. They also enhance reporting accuracy and technician assignment.

👉 How to Define Work Order Types:

  1.  Go to the Field Service app.
  2.  Navigate to Settings → Work Order Types.
  3.  Click “+ New” to create a new type.
  4.  Provide a name and description.
  5.  Optionally associate it with default incident types or templates.

2. Work Order Status

Every work order in Field Service passes through multiple lifecycle stages before being billed. These include:

  •  Open – Unscheduled: Created but not yet scheduled.
  •  Open – Scheduled: Assigned to a technician but work hasn't started.
  •  Open – In Progress: Technician is actively working.
  •  Open – Completed: Work is done but waiting for review.
  •  Closed – Posted: Final approval done; billing can proceed.
  •  Closed – Canceled: Job was canceled and won’t be billed.



⚠️ Note: It’s recommended not to modify these default statuses. They are linked to core system workflows and altering them may break related functionality.

 3. Work Order Sub Status

Sub statuses add more context to a work order’s main status. For example:

  •  Status: Open – Unscheduled
  •  Sub Status: Waiting for Parts or Pending Customer Signature
  •  Status: Open – Completed
  •  Sub Status: Follow-up Required

These can also influence scheduling behavior. For example, a sub status of “Parts Not Received” could prevent the job from appearing on the scheduling board until the parts arrive.

 To Configure Sub Status:

1. Go to Settings → Work Order Sub Status.

2. Click “+ New”.

3. Define:

  •     Name (e.g., Awaiting Parts)
  •     System Status it relates to (e.g., Open – Unscheduled)
  •     Set as Default (if it should be automatically selected)


Best Practice: Think strategically about sub status usage. For example, if you want only “Ready for Scheduling” jobs to show on the schedule board, you must customize the resource requirement view accordingly.


Summary of Benefits:

  •  Efficient classification of jobs
  •  Enhanced visibility into job progress
  •  Controlled scheduling logic
  •  Streamlined reporting and analysis

Comments

Post a Comment

Popular posts from this blog

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

Connecting the Dots: FetchXML and Web API Integration in Dataverse

Image
 In Dataverse, FetchXML and the Web API are two powerful mechanisms for retrieving data and interacting with entities. Here's a brief overview of each and how they can be integrated: 1.    FetchXML :      -   Definition:   FetchXML is a proprietary query language used in Microsoft Dynamics 365 and Dataverse for querying data from entities.    -   Usage:   FetchXML queries can be used to retrieve data based on complex criteria, perform aggregations, and filter records.    -   Features:   FetchXML supports various query expressions, including conditions, sorting, grouping, and aggregation functions.    -   Integration:   FetchXML queries can be executed programmatically using client-side scripting, server-side code, or through tools like the Dynamics 365 Web API. 2.    Web API :      -   Definition:  ...
Read more