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
Need help with this product?

We can help you with Dynamics 365 Field Service : Add status and sub-status information to a work order

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

From Conversations to Automation: Understanding Microsoft Copilot Studio

In November 2023, Microsoft announced that Power Virtual Agents was becoming part of Microsoft Copilot Studio. Microsoft now characterizes Cop...

12 days ago

Copilot Studio: Agent Integration Approaches — Tools, Knowledge, and Agents

In Copilot Studio, agent integration employs the same fundamental integration concepts and patterns used in traditional enterprise integration...

2 months ago

Copilot Studio: How to Plan Integration with Enterprise Systems

Integrating Microsoft Copilot Studio agents with enterprise systems transforms a basic chatbot into a secure, intelligent digital teammate tha...

2 months ago

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...

2 months 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...

2 months 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...

2 months 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...

3 months 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...

4 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.