Creating a Recurrence Series
Create a calendar-based series from an existing case or CRM task. Use a case as the primary record when each occurrence needs a separate service request. Use a CRM task when the repeated unit is the visit itself.
The primary case or CRM task remains the first occurrence. Background processing creates a supporting Field Service Recurrence record and later occurrences. Manage the series through the case or task controls. The definition is hidden from normal access in the NetSuite user interface.
For field definitions and record relationships, see FSM Recurrence Record, FSM Case Record, and FSM CRM Task Record.
Before You Begin
Recurrence must be enabled for the account, and its controls must be available on the selected record. Recurrence is disabled in the standard configuration.
Start with a saved case or CRM task that is not already in a recurrence series. To prepare a case, use Creating a Case in NetSuite. Creating a CRM task is a separate prerequisite when no suitable primary task exists.
For recurrence patterns, copied values, generation limits, and calendar constraints, see FSM Case and Task Recurrence.
Required references, including assignment, must remain valid when later occurrences are saved. For recurring cases with child visits, applicable Case Program rules must be configured separately.
To create a recurrence series:
-
Go to the list for the record you want to repeat:
-
For a case, go to Field Service > Cases > Cases.
-
For a CRM task, go to Field Service > Tasks > Tasks.
-
-
Open the intended primary case or CRM task for editing.
Review its service details, customer, Company, asset, assignment, Field Service Start Date, and service time zone.
-
In the Recurrence section, select daily, weekly, monthly, or yearly in Type.
-
In Interval, enter a positive whole number and complete the pattern values:
-
For a weekly pattern, select the weekdays in Day of Week.
-
For a monthly pattern, select Month Pattern and complete Day of Month or Day of Week as applicable.
-
For a yearly pattern, review the read-only Month supplied from Field Service Start Date. Complete the applicable monthly pattern values.
Daily intervals use calendar days. The recurrence calculation does not automatically skip weekends or public holidays.
-
-
In End Type, select the end condition:
-
Select None for an open-ended series.
-
Select After and enter End Count. The count includes the primary record.
-
Select By and enter End Date. The date must be later than the start date.
-
-
Click Save.
After Saving the Primary Record
Saving updates the primary record and requests recurrence processing. Background processing creates the supporting recurrence definition and links the primary record to it. FSM creates later case or CRM task records using that definition.
After processing, review Recurrence Instances and open the saved occurrences. Confirm their record type, dates, copied service values, and recurrence relationships.
The configured generation horizon limits how far ahead FSM creates occurrences. The standard horizon is 90 days, subject to the end condition. An open-ended series is extended over time rather than created indefinitely in one operation.
The following table distinguishes the resulting records.
|
Primary Record |
Result |
|---|---|
|
Case |
Later occurrences are case records. The primary case's child CRM tasks are not copied. Case Program rules can create visits for each occurrence. |
|
CRM task |
Later occurrences are CRM task records. No case series is created. The standard copied-field list omits the case relationship, so confirm any required case links separately. |
For child visits on recurring cases, review automatically generated tasks first. If expected tasks are missing, use Generating CRM Tasks for a Case with Program.
For the separate case-series and child-task generation stages, see FSM Recurring Cases with Program Tasks.