9
Or Field Service customers often ask how to set something like this up: Incident Type A monthly Additionally Inc Type B every quarter Additionally Inc Type C every year So that a yearly maintenance job consists of Inc Type A,B and C but a monthly job contains only A. Another example: If you have a monthly maintenance and a yearly for the same Customer/Asset/Location, how to set that up? Today you either need a) to create a monthly Agreement Booking Setup, than delete each 12th Agreement Booking Date AND create another yearly Agreement Booking Setup. OR b) create for each month a different Agreement Booking Setup or another even stranger logic (every 2. month plus x ...) b) isn't really nice and a) doesn't always stay consistant. There are some cases where all Agreement Booking Dates that haven't been processed (WO not generated) are deleted and recreated again from scratch: - change the pre- post booking flexibility - add a Custom Date in Booking Recurrence dialog - Add preferred start time - extend duration of Agreement (postpone Agreement.'End Date') - ... Both of the ways aren't how a customer would want to set up Agreements.
Category: Agreement
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. We love this idea.

Interestingly, this is something we've been discussing as part of our roadmap; however, we do not currently have concrete plans to implement it. Anything you can do to get this idea more votes will help us increase the priority of this feature in future planning discussions.

Thanks for sharing,
Jason Cohen
PM - Dynamics 365 Field Service

Comments

M

What is different from setting up 3 different Booking setups, each with its own recurrence, on the same Agreement?

Category: Agreement

M

Very much necessary.
We built this on our own with a plug-in, but this was a somewhat expensive solution for something which seems to be a basic requirement in maintenance based businesses.

Category: Agreement

M

We are in the process of setting up Dynamics 365 Field Service in our organization and not having this option really is an issue to properly setup preventive maintenance schedules.
At the moment we use the service agreements in the Service Management module of MS Dynamics AX (2012 R2) and in there this option is present, so basically it is a step back from AX in 2012!

Category: Agreement