Check-in time: This value is present in the agreement and specifies when agreed data, such as booking data and work orders, should be generated on the date of the day. This is useful because some organizations don`t want agreements that generate a lot of orders in the middle of a workday, while dispatchers plan and manage other orders. You also set custom date orders that need to be executed if a model doesn`t reflect your business needs. For example, perhaps an agreement to perform the service on different holidays throughout the year. Incident types are available for all versions of Dynamics 365 Field Service. However, the use of incident types with multi-resource planning group models is only available with Field Service v8.0. In addition to a reservation system, each agreement can also, as an option, be equipped with a billing device. Each billing establishment contains one or more billing products. Both the agreement booking settings and the schedule for calculating the agreement can be repeated. You can have an annual agreement on the weekly service of a device. B but you charge every month.

In order to plan this task, the necessary resources have a duration corresponding to the duration of the event (in our example 2 hours) and the feature is also passed on. The incident you want to add to an agreement may be slightly different from the one you would add to a single task that is not part of an agreement. For example, the incident would normally require 1 hour of a service, but for the agreement, you negotiated with the customer 2 hours of a service. Instead of creating a second type of incident only for this agreement, you can set «Copy incidents on agreement» to «No,» add the incident to the agreement, and then manually add specific service tasks, product, services, etc. In this way, you can use the same type of incident that will later be useful for reporting. Set this «Yes» option and incident elements are added to the agreement, and you can accept these items or make minor variations from there.