Dynamics 365 Field Service: Scheduling Inspections Every 5, 10 or Even 20 Years – Yes, It’s Possible
One of the strengths of Dynamics 365 Field Service Agreements is the ability to automatically generate recurring Work Orders for preventive maintenance, inspections, and service activities. Organizations commonly use agreements for monthly, quarterly, or annual visits. Microsoft even highlights agreements as the standard mechanism for recurring inspections and maintenance schedules. [learn.microsoft.com]
But what happens when your business requirements don’t fit the traditional recurrence patterns?
The Challenge
During a recent Field Service implementation, business users needed to schedule regulatory inspections and diagnostics on customer assets at very long intervals:
- Every 5 years
- Every 10 years
- Every 20 years
Examples include:
- Safety inspections
- Infrastructure certifications
- Industrial equipment diagnostics
- Compliance-driven audits
At first glance, Customer Agreements seem like the perfect fit. However, consultants quickly run into two challenges:
1. The scheduling logic starts from a deadline date
The business wanted future Work Orders to be calculated relative to a certification or expiration deadline rather than a simple recurring maintenance schedule.
2. The recurrence UI appears limited
The Agreement Booking Recurrence dialog is designed around familiar patterns such as:
- Daily
- Weekly
- Monthly
- Yearly
There is no obvious “every 10 years” or “every 20 years” option in the user interface.
As a result, many consultants assume that these scenarios require custom development or Power Automate automation.
The Investigation
While researching the issue, we reviewed Microsoft documentation on Agreements and several community implementations. Microsoft documents that agreements rely on recurrence definitions and allow recurrence patterns to be stored behind the scenes as recurrence settings.
We also found community examples showing how yearly recurrence patterns can be generated programmatically by populating the recurrence settings directly.
However, the key question remained:
Can standard Field Service Agreements support 5-year, 10-year, or 20-year interventions without customization?
Resolution: Think in Months, Not Years
Following investigation and feedback from the Product Group, the answer is yes.
Although the recurrence dialog doesn’t make this obvious, the underlying recurrence engine supports large monthly intervals.
Workaround
Instead of choosing a yearly recurrence:
- Set the recurrence pattern to Monthly
- Configure Occur every X months
Examples:
| Requirement | Monthly Interval |
|---|---|
| Every 5 years | 60 months |
| Every 10 years | 120 months |
| Every 20 years | 240 months |
Example: Inspection Every 10 Years
Configure the Agreement Booking Setup recurrence as follows:
- Pattern: Monthly
- Occurs Every: 120 Months
- Start Date: Inspection baseline date
- End Date: As required by the agreement lifecycle
The recurrence engine will create booking dates every 120 months, effectively resulting in a 10-year inspection cycle.
Similarly:
- 60 months = 5 years
- 240 months = 20 years
No custom code required.
Why This Works
Behind the scenes, the Field Service Agreement recurrence engine stores recurrence information independently from the simplified user interface. Microsoft documentation also notes that recurrence definitions contain frequency values that can be imported and configured beyond the visible wizard options.
The UI may not explicitly advertise multi-decade schedules, but the recurrence engine is capable of handling them when expressed as monthly intervals.
Things to Consider
Before implementing very long-running agreements, consider the following:
Agreement Duration
Ensure the Agreement End Date is sufficiently far in the future to cover the required cycles.
Work Order Generation Horizon
Verify the Generate Work Order Days in Advance configuration aligns with your operational planning horizon.
Asset Lifecycle Changes
Over a 10- or 20-year period:
- Assets may be replaced
- Ownership may change
- Regulatory requirements may evolve
Some organizations therefore prefer combining Agreements with review processes before automatically generating future Work Orders.
Reporting and Visibility
Because interventions are generated so far apart, consider adding:
- Compliance dashboards
- Upcoming inspection views
- Power BI alerts
- Review workflows
This helps ensure long-term inspections don’t become invisible until the due date approaches.
When Customization Might Still Be Needed
The monthly workaround solves the recurrence challenge, but customization may still be required when:
- The next inspection date is calculated from a certification result.
- Inspection intervals vary dynamically based on risk levels.
- Regulatory deadlines are recalculated after each inspection.
- Complex compliance rules determine the next service date.
In those cases, Power Automate or custom scheduling logic may still be appropriate.
Conclusion
If you’re implementing Dynamics 365 Field Service and need to schedule inspections every 5, 10, or even 20 years, don’t assume customization is required.
A simple but not-so-obvious configuration can achieve the requirement:
✅ Set recurrence to Monthly
✅ Use 60, 120 or 240 months as the interval
✅ Leverage the standard Agreement framework
It’s a great example of how the underlying Field Service platform is often more flexible than the user interface suggests—and sometimes the solution is simply thinking in months instead of years.
