Loading...

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

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

Published on:

Learn more
Need help with this product?

We can help you with Dynamics 365 Field Service : Configure work order types and work order resolutions

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

Power Platform , D365 CE & Cloud
Power Platform , D365 CE & Cloud

Dynamics 365 CE, Power Apps, Powerapps, Azure, Dataverse, D365,Power Platforms (Power Apps, Power Automate, Virtual Agent and AI Builder), Book Review

Share post:

Related posts

Book Review : The Manager 's Path : A Guide for Tech Leaders Navigating Growth and Change by Camille Fournier

 After a long time, I came across a book that is truly valuable for engineering students and professionals, especially those working in t...

1 hour ago

Power Platform Environment Deep Dive (Part 2)

In Microsoft Power Platform, choosing the right environment type is important because each environment is designed for a different business pu...

11 days ago

Power Platform Environment Deep Dive (Part 1)

Today, in the business enterpriese world, Power Platform enables organization to build application, automate workflow, analyze data  crea...

13 days ago

Book Review : Life 3.0 by Max Tegmark

This is the third book I’ve read this year, and even though I’m still in the early chapters, it already feels like my favorite read of the yea...

1 month ago

Dataverse Views Demystified: Making Data Work for You

In Microsoft Dataverse, users do not always see all the data stored in a table. What they can view depends on their security permissions, role...

2 months ago

Decode & Fix : Shared App host initialization has timed out in Microsoft Power Apps

 Issue :While working with apps in the Microsoft Power Platform, we encountered a critical issue where the application failed to load pro...

5 months ago

Dataverse Integration Patterns: Sync vs Async vs Event-driven (Real Use Cases)

As organizations start using Microsoft Power Platform, Microsoft Dataverse is no longer just a place to store data—it becomes a key part of ho...

5 months ago

Book Review : Don't Believe Everything You Think by Joseph Nguyen

My second book of this year is "Don’t Believe Everything You Think" by Joseph Nguyen. This book was recommended by a friend who strongly belie...

6 months ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.