The Field Service Lightning (FSL) bundling feature allows multiple Service Appointments (SAs) to be grouped into a single parent Bundle Service Appointment for scheduling efficiency. This grouping is governed by various related policies, the most relevant being the Appointment Bundle Restriction Policy.
A Restriction Policy defines which Service Appointments can or cannot be bundled together based on common field values.
The Allow Empty checkbox on the Appointment Bundle Restriction Policy controls how Service Appointments with empty restriction field values are handled during bundling:
Image description: Screenshot of the Appointment Bundle Restriction Policy configuration page in Salesforce Field Service, showing the 'Allow Empty' checkbox. The screenshot demonstrates the policy setup where restriction field values control which Service Appointments can be grouped together in a bundle.
Real-life example: If your Restriction Policy is based on the Work Type field and some Service Appointments have no Work Type assigned (empty value):
Note: To fully avoid the bundling of Service Appointments with empty field values, you can use Recordset Filter Criteria for Bundling Appointments logic in the Bundler Policy. See Create Recordset Filter Criteria for Bundling Appointments.
Note: To fully avoid the bundling of empty values, you can use Recordset Filter Criteria for Bundling Appointments logic in the Bundler Policy.
Please refer below documentation: Create Recordset Filter Criteria for Bundling Appointments
The Appointment Bundle Restriction Policy in Salesforce Field Service Lightning (FSL) uses the Allow Empty setting to control how Service Appointments (SAs) with missing restriction field values are grouped during scheduling.
Summary of behavior:
005229024

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.