Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Field Service updates!Learn about the key capabilities and features of Dynamics 365 Field Service and experience some of the new features.
Download overview guide | Watch Field Service video
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a Yearly maintenance schedule and a monthly schedule on an asset..
I.e I require
* 11 Monthly bookings Jan - Nov
* 1 yearly booking in Dec
How can I set this up, I can see no way to do a monthly every month for 11 months per year
I just had a quick look and I dont think there is a way to achieve it in a nice enough way.
You could just merge the yearly December booking into the Monthly bookings but I can understand that they may have different tasks assigned to them.
Or you could do custom dates? How long do your agreements usually last?
It could be done with custom dates but this creates a lot of setup and ongoing maintenance . Contract may be 1 -5 years and then renewals etc. We have hundreds of sites and hundreds of maintenance schedules so need a automated rollover over contract period /renewal.
Ideally need be to be able to configure monthly X months per year on recurrence. I guess I could set up 11 sep 1 month a year schedules but again higher maintenance
Following structure should be able to support this scenario:
1. Create an agreement record with 2 agreement booking setup records
-- 1. Agreement Booking Setup with recurrence: 12x months
-- 2. Agreement Booking Setup with recurrence: Once a year
For the first ABS, delete/deactivate the 12th instance of the Agreement Booking Date record.
This is generally called 'suppression', it is not an out of the box feature yet.
Yeah, deactivating the 12th agreement booking date record is definitely an option. I would probably go for this.
Thanks for this, Yes I can use the Cancel status ( or deactivate) to skip a WO being generated for a single booking Date.
However this requires manual maintenance on each monthly scheduled ( have 100's), and cannot be done until the booking itself is generated dependent on "Generate Booking Dates X Months In Advance "which must be set to at least 12 months or the length of the contract to do this during /just after setup.
It will also require another manual change each year of the contract when future bookings get generated
All of this is prone to user error and has a high maintenance overhead.
I am looking for a way to do this once at setup, however it does not appear possible with current capability. The suppression would need to be based on the generic moth - rather than an actual booking date e.g .Monthly excluding Dec
If suppression is based on month only (versus weeks, days or counters), this 'month number' could be maintained at the Agreement Booking Setup record and then Power Automate flow can automatically cancel Agreement Booking Date record (it doesn't need to wait for Booking / Work Order to be generated). This idea (or other similar solutions) can be explored with minor configurations/customisations.
All great suggestions on the thread. In addition please note it is on our radar to try and make this easier out of the box but no date commitments yet.
Yes that would be the easiest way in the short term to automate this. Thanks
Great that this is being looked at for future improvement.
It is a regular occurrence for a Service Company to have Monthly and yearly service/inspections so OOB support would be appreciated
I have lots of agreements that are created via a plugin and they have a normal and annual agreement setup.
The annual is set to one day after the normal and triggers another plugin which retrieves the normal booking dates and cancels the booking date which is the annual date -1.
The rationale of 1 day after is so that the normal date will always be populated before the annual.
The only issue here is if someone makes a change on the normal agreement setup and not the annual it repopulates all the normal dates and the canceled date will be active.
This has been working well for several years now and could be done with a flow as well.
Good to hear that, Gedda. Can you please mark my response as a verified answer. Thanks
Business Applications communities