Resource Requirement is to a Planner what laptop is to a Programmer. Okay this is a bit too cliched but the fact is, as a planner, you’d mostly work on these three entities in Dynamics 365: A Resource Requirement record sits at the heart of URS and Field Service. The record basically defines the shape and form of the booking to fulfil the need. When a booking is created on a Schedule Board (drag and…
One of the FAQs on Dynamics 365 Field Service capabilities is about hourly rates of resources and how does that reflect the costing of work orders. This quick article will show a demo of how Dynamics 365 Field Service maintains and use hourly rates in work order bookings. Step 1 Let’s begin with setting up an hourly rate for a resource. Go to Resource view, open a resource and update hourly rate in Field Service…
One of the latest features announced for Release Wave 1 2020 in Dynamics 365 Field Service is the ability to ‘configure’ when the system should be generating Booking Timestamps. What is it and why does this matter?Booking timestamps is an entity which gets auto-populated to record updates on the status of booking/work orders. It records two important things: status and timestamp. When a Work Order and associated Booking goes through status changes, booking timestamp maintains…
Work Orders can be automatically generated and bookings can be auto-generated by Dynamics 365 Field Service, thanks to the Agreements functionality in the system. Agreements are used for setting up preventative maintenance schedule, audits, equipments/fleet service schedule etc. in the system, which then generates work orders and booking automatically – resulting in obvious productivity gains. One of the key steps in setting up agreements is to setup recurrence of the work orders (and subsequently but…