Guidelines for Recordset Filter Criteria
Field Service filter criteria let you match records in one object against records in another. For example, you can choose criteria to filter which service appointments can be scheduled during a shift.
Required Editions
| Available in: Lightning Experience |
| The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions. |
| User Permissions Needed | |
|---|---|
| To view, create, and update recordset filter criteria for shifts | View, create, and edit on Recordset Filter Criteria and Recordset Filter Criteria Rules AND View on the filtered object, source object, and filtered object’s fields AND Delete on Recordset Filter Criteria Rules |
Recordset Filter Criteria Considerations
Keep these considerations in mind when you create and edit recordset filter criteria.
-
Only Recordset Filter Criteria marked Active are used in scheduling.
-
When you add multiple filter conditions, only appointments matching all the conditions can be scheduled.
-
The Value input changes depending on the service appointment field you choose. For example, picklist fields show the list of available choices.
-
You can’t match on text field values that include apostrophes (
’), commas (,), or double quotation marks (”). -
Users without access to a service appointment field used in a filter condition don’t see the field name or value. They also can’t edit or delete the filter condition.
-
When you use inline edit on a recordset filter criteria, the filter conditions are shown in the related list. You can manage filter conditions individually from the related list. Or to see all the filter conditions in one place, use the Edit action.
-
The Recordset Filter Criteria field must be added to the Shift page layout.
- After you add a custom field to the filtered object, it can take around 15 minutes for the new field to appear in the Criteria Field picklist.
- You can add a maximum of 5 considerations to the Recordset Filter Criteria field.
- The asset fields Availability, Reliability, Average Time to Repair, and Average Time Between Failures are calculated internally, so they can’t be used to define Usage-Based, Usage-Counter, or Usage-Duration rule types.
Guidelines for Custom Logic
- Build the filter logic with parentheses and the AND or OR Boolean operators. To group conditions, use parentheses around the parameters, for example 1 AND (2 OR 3). If you add another condition, the custom logic is updated automatically to 1 AND (2 OR 3) AND 4.
- Every index must have a corresponding recordset filter criteria rule, but every rule doesn’t need to be used in the custom logic.
- If no custom logic is defined, all recordset filter criteria rules are treated with an AND, meaning all conditions must be True.
- You can’t delete a recordset filter criteria rule that’s referenced in custom logic.
Alternatively, you can follow these steps:
- Update RFC.CustomLogic as empty, or remove the index reference in custom logic.
- Delete the recordset filter criteria rule.
- Update RFC.CustomLogic with the correct value.
