Loading...

Dynamics 365 Field Service : Add products and services to incidents

Dynamics 365 Field Service :  Add products and services to incidents

When delivering field service, standardizing how issues are resolved helps improve efficiency, consistency, and customer satisfaction. Dynamics 365 Field Service supports this through Incident Types, which represent common service scenarios like "Air Conditioner Maintenance" or "Boiler Repair."



To ensure technicians have the right materials and tasks, you can associate products and services directly with these incidents. This blog will walk you through:

 What are Incident Types?

  •  Why add products and services to incidents?
  •  How to configure products and services for incident types
  •  Best practices

What are Incident Types?

An Incident Type defines a standardized issue or problem your organization often deals with. Each incident type may include:

  •  Predefined service tasks (what needs to be done)
  •  Required products (materials or parts)
  •  Required services (billable or internal time/labor)

By assigning these to incident types, work orders become more accurate and faster to create.

Why Add Products and Services to Incident Types?

Adding products and services to an incident type provides:

  • Automation: Products and services are auto-added to work orders based on the incident.
  • Cost Estimation: Helps estimate total cost and time.
  • Consistency: Ensures every technician follows the same playbook.
  • Inventory Management: Prepares for part availability and reservation.
  • Reusability: Easily reused across multiple work orders.

How to Add Products and Services to Incident Types

Here’s how to configure products and services for an incident type.

 1. Navigate to Incident Types

  •  Go to Field Service > Settings > Incident Types
  •  Open an existing incident or create a new one

 2. Add Products

  •  Go to the Products tab under the incident type form
  •  Click + New Incident Type Product
  •  Fill in:

    •    Product: Choose from available inventory items (e.g., HVAC filter)
    •    Quantity: Number of units required
    •    Unit: Unit of measure
    •    Price List (optional): For calculating costs
    •    Default: Choose if this should be added to every related work order

 Note: Products can be chargeable or internal.

 3. Add Services

  •  Switch to the Services tab
  •  Click + New Incident Type Service
  •  Fill in:
    •    Service: The type of labor (e.g., AC technician visit)
    •    Estimated Duration: Time required to complete the task
    •    Price List (optional): Set a billing rate
    •    Billing Type: Choose chargeable or non-chargeable

 Services help plan labor time and costs effectively.

Example Scenario

Let’s say your field service team often performs "Water Heater Repair."

Create an incident type named "Water Heater Repair" and link:

  •  Product: Heating Element (Qty: 1)
  •  Product: Teflon Tape (Qty: 1)
  •  Service: Technician Visit (Estimated Duration: 2 hours)

Whenever a dispatcher creates a Work Order for this incident, these items will be automatically added, ensuring nothing is missed.

Conclusion

By associating products and services with incident types in Dynamics 365 Field Service, your organization can drastically improve its efficiency, accuracy, and customer experience. This approach minimizes manual errors and ensures that your technicians are always prepared with the right tools and tasks.

Published on:

Learn more
Need help with this product?

We can help you with Dynamics 365 Field Service : Add products and services to incidents

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

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

12 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

Book Review : Scary Smart by Mo Gawdat

The first book I read in 2026 was Scary Smart by Mo Gawdat, the former Chief Business Officer at Google.In today’s world, Artificial Intellige...

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.