Customer Engagement & Dynamics CRM Forum

 View Only
  • 1.  Agreement booking dates not generating as expected

    Posted Feb 27, 2020 08:58 AM
    I have created an agreement in Field Service (solution v and I am trying to set up quarterly recurring work orders. I believe (possibly incorrectly) that if I followed the instructions in the docs (

    then the system would generate 4 booking dates 3 months apart. However it never generates booking date records beyond more than 1 month after the start date. 

    I have experimented with recurring agreement booking dates on other schedules and those work up to the 30 day window as well? How do I get it to generate booking dates for the entire year?

    The ultimate goal would be to use the booking dates to chart out how many jobs (or hours of work) are planned for any given week or month across the year so that when a new client comes on board, the user can see which weeks or months have the most availability. It would also be helpful to use those dates together with the incident products to plan on ordering inventory.


    Nelson Johnson, Solution Architect
    BroadPoint, Inc., Bethesda MD
    Link with me!

  • 2.  RE: Agreement booking dates not generating as expected
    Best Answer

    Posted Feb 28, 2020 01:48 AM
    Edited by Nelson Johnson Feb 28, 2020 09:00 AM
    Nelson, go to the Field Service Settings​ record and click on the Agreement tab. From there you will see a setting called Generate Booking Dates X Months in Advance, update that to 12. The next time you create an agreement you should see it create booking dates up to 12 months into the future and be able to build-out your utilization charts/dashboards. I am pretty sure it is only going to work for newly created agreements, but I have not actually tested it.

    Hope this helps,
    Rob Pike
    Minneapolis, MN

  • 3.  RE: Agreement booking dates not generating as expected

    Posted Feb 28, 2020 04:06 PM
    This is a global setting (Generate Booking Dates X Months in Advance), but only takes effect for a given Booking Setup when the background Field Service workflow that generates the Booking Dates gets re-evaluated.  So especially if you have long frequencies, then it may take a period of time (months) for the change to reflect across all Booking Setups unless you force the re-evaluation.

    One word of caution is that if you force re-evaluation in bulk or have a lot of setups running on the same re-evaluation cycle, then it can hit a lot of load on the system at the same time generating all the new Booking Dates.  For example you can imagine the number of records if you had a weekly recurrence on a lot of setups and changed the setting from 2 months in advance to 12 months in advance.  But I think you're just in a trial / prototyping mode so this won't affect you.

    I don't know whether existing active Booking Dates are removed if you reduce the months in advance setting, or whether time needs to take its course as the current dates are move into the past.

    Robert Ward
    Chubb Australia

If you've found this thread useful, dive deeper into User Group community content by role