Loading...

Dynamics 365 Field Service : Add status and sub-status information to a work order

Dynamics 365 Field Service :  Add status and sub-status information to a work order

Work orders are at the heart of Dynamics 365 Field Service. They represent service requests or jobs that need to be completed—whether it's a repair, installation, or maintenance task. To track their progress effectively and give teams better visibility, Dynamics 365 allows you to assign both a status and a sub-status to each work order.

Let’s explore what these are and how to set them up.

What is a Work Order Status?

The system status reflects the current stage in the lifecycle of the work order. Some common statuses include:

  •  Open – Unscheduled
  •  Open – Scheduled
  •  Open – In Progress
  •  Open – Completed
  •  Closed – Posted
  •  Closed – Canceled

These statuses are system-defined and drive workflow automation, resource scheduling, and billing behavior.

What is a Sub-Status?

While the system status tells you the broad stage, the sub-status provides additional context or detail. It's customizable, allowing organizations to reflect more granular stages within each main status.

 Example:

 System Status: Open – Scheduled

 Sub-Status: Waiting for Parts, Ready for Dispatch, Technician , Route

Sub-statuses help field teams, dispatchers, and back-office staff better understand the current situation without changing the main workflow.

How to Add or Modify Sub-Status in Dynamics 365 Field Service

1. Go to Field Service App

  • Navigate to the Field Service app in your Dynamics 365 environment.

2. Open Advanced Settings

  • Click the gear icon and choose "Advanced Settings."

3. Go to Sub-Statuses

  • In the sitemap or under Settings > Field Service Settings, find “Work Order Sub-Statuses.”

4. Create a New Sub-Status

  • Click + New
  • Set the name (e.g., "Awaiting Customer Confirmation")
  •  Link it to the appropriate System Status (e.g., Open – Scheduled)
  •  Set visibility and default options if needed

5. Save and Publish

6. Use in Work Orders

 Now, when creating or updating a work order, users can select the appropriate sub-status to reflect real-time progress.

Why Use Sub-Statuses?

  •  Adds transparency into work order progress
  •  Improves communication between field technicians and back office
  •  Enables better filtering, reporting, and dashboards
  •  Provides data for service optimization and customer satisfaction analysis

Real-Life Example

Imagine a field service company that installs HVAC systems. The system status might be "Open – Scheduled," but the sub-status can help teams know if the parts are ready, if the customer has confirmed the time, or if the technician has left for the site.

This kind of visibility is a game-changer for customer communication and efficient scheduling.

Conclusion

By customizing and using sub-statuses effectively, organizations can greatly enhance the value of work orders in Dynamics 365 Field Service. It turns a basic status update into a powerful operational tool—fueling better coordination, insights, and service delivery.

👉 Learn more or step through it on our blog:

🔗 Add Status and Sub-Status Information to a Work Order

Published on:

Learn more
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

Dynamics 365 Field Service – Optimize multiple resources with Scheduling Operations Agent

We are announcing the ability to optimize multiple resources with Scheduling Operations Agent in Dynamics 365 Field Service. This feature will...

3 days ago

How We Successfully Removed the Resco Woodford Managed Solution from Dynamics 365 Field Service

Recently, we needed to remove the legacy Resco MobileCRM (Woodford) managed solution from a Dynamics 365 Field Service environment. Although t...

4 days ago

Unable to Delete Work Order Due to “The Time To Promised Must Be Later Than The Time From Promised” exception – Dynamics 365 Field Service

While attempting to delete a historical Dynamics 365 Field Service Work Order, we encountered the following error: Exception Message: The time...

10 days ago

Dynamics 365 Field Service – Explore Dataverse data with Microsoft 365 Copilot

We are announcing the ability for service managers, dispatchers, and back-office teams to query work orders, bookings, service history, and as...

1 month ago

How to Optimize Mobile Offline Profiles Using FetchXML in Dynamics 365 Field Service

In many Field Service implementations, mobile offline capability is essential, especially for technicians working in low or no network areas. ...

2 months ago

We need to talk about... Dynamics 365 Field Service... Release Wave 2 for 2025

Next in my blog, I will launch a series on the changes we can expect to see as part of Release Wave 2 for 2025. Microsoft’s 2025 Release Wave ...

3 months ago

Dynamics 365 Field Service: Optimize schedules with Scheduling Operations Agent

The Scheduling Operations Agent for Dynamics 365 Field Service enables dispatchers to quickly and easily optimize schedules for technicians as...

3 months ago

How to Use Copilot to Create Inspection Templates in Dynamics 365 Field Service from PDF and Image Uploads (2025 Guide)

Microsoft’s Dynamics 365 Field Service mobile app empowers field technicians to manage tasks, log inspections, and ensure compliance directly ...

8 months ago

Dynamics 365 Field Service – Tailor Copilot chat experience with Copilot Studio

We are announcing the ability of makers being able to customize their experience of the Copilot side pane by using the customization capabilit...

9 months ago

Fixed – Workflow must be in Published state (Dynamics 365 Field Service)

Recently, we got the following error while booking a resource in our schedule board. We earlier got the same error while trying to delete book...

9 months ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy