You are a Dynamics 365 for Field Service Dispatcher reviewing automatically generated bookings for optimization of the schedule. You notice that, for…

When a work order is auto-generated from an Agreement Booking Setup, it inherits details like service tasks, products, and services. The primary source for these details is the Agreement Booking Setup itself. These details are often populated from a related Incident Type. A common point of failure is the "Copy Incident Items to Agreement" setting on the Incident Type; if set to "No," items won't be copied to the Agreement Booking Setup. Therefore, you should first check if the Agreement Booking Setup itself contains the required items, and second, verify the "Copy Incident Items" setting on the source Incident Type to ensure the copy process is enabled.

A. While the Incident Type should contain the items, the more direct issue is whether they were successfully copied to the Agreement Booking Setup, which is the direct source for the work order.
C. This setting must be "Yes" for work orders to be generated at all. Since the scenario states work orders are being generated (but are empty), this setting is not the problem.

1. Microsoft Learn. (2023). Set up agreements. In Dynamics 365 Field Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/field-service/set-up-customer-agreements. Under the "Agreement booking incidents" section, it explains how incident types add predefined work order details to an agreement and subsequently to work orders.

2. Microsoft Learn. (2023). Create incident types. In Dynamics 365 Field Service documentation. Retrieved from https://learn.microsoft.com/en-us/dynamics365/field-service/create-incident-type. This document describes the function of incident types as templates and implicitly covers the flow of information from the incident to the work order via the agreement.