Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Field Service updates!Learn about the key capabilities and features of Dynamics 365 Field Service and experience some of the new features.
Download overview guide | Watch Field Service video
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
What is the 'right' way to handle multiple jobs on a single work order - multiple Service Tasks or Incident Types or something different? We need this functionality primarily for our Planned Maintenance that typically requires routine checking of many small assets (e.g. air conditioning units) performed by one technician at a single site that will result in a single invoice. The technician would need the ability to record each asset they worked on.
Both options are OK. Since these are planned maintenance jobs, you may want to set up Agreements to generate jobs automatically and use assets on either ‘agreement booking service task’ or ‘agreement looking incidents’. The differentiation between these two options relates to how the job will be performed. If each asset’s servicing requires specific products or capabilities (characteristics) then incident type is a better option otherwise service task would be a way to go. Service tasks will also make it easy for technicians to quickly mark all of them as completed.
Please mark as verified if the answer is helpful. Thank you.
- Ali (I write about D365 Field Service related exciting stuff at [https://akhan.me](https://akhan.me/))
Business Applications communities