Appointment Bundling Limitations

Aggregation Duration Downscales

• When you define more than one aggregation duration downscale, they aren’t evaluated in any particular order. If your duration downscales include overlapping service appointments and include Max Reduction values, it can lead to inaccurate results.
• Custom fields for service appointments used in aggregation duration downscales must have read and edit access.

See Create Appointment Bundle Aggregation Duration Downscales.

Aggregation policies

• Custom fields for service appointments used in aggregation policies must have read and edit access.
• For the Allow the same value to appear more than once option, make sure that Do not allow duplicate values isn’t selected in the field’s configuration settings.
• For string aggregations with the Sum Based on Bundle Members action, make sure that the length of the string field can contain enough values to populate the bundle service appointment field.

See Create an Appointment Bundle Aggregation Policy.

Bundle Member Service Appointments related list

• The Sort By option is set to Default. Other options aren’t supported.
• The expanded view of the related list indicates that the appointments are sorted by due date, even if the order is determined by the Appointment Bundle Sort Policy.
• Using the arrow that changes the order of the appointments according to a specific column overrides the order determined in the Appointment Bundle Sort Policy.

Bundle policies

• The Allow Scheduling Dependencies in Bundle field isn’t supported.
• You can create more than one service territory policy for a bundle policy, but it isn’t recommended. The dispatcher can only bundle together service appointments with the same service territory in the same time zone. If you define more than one service territory for a bundle policy, make sure that the enhanced scheduling and optimization setting in all the service territories matches. If the setting is enabled in one service territory and disabled in another, the bundles created with the bundle policy can’t be updated.
• You can delete a bundle policy even if it’s already in use. However, you can’t perform actions on a bundle that was created using that policy, such as add or remove bundle members or unbundle a bundle.
• Custom fields for service appointments used in bundle policies must have read access.

See Create an Appointment Bundle Policy.

Experience Site users

Experience Site users don’t have the Bundle Policy field in the service appointment’s Bundle tab. See Add Permissions for Service Appointment Bundling.

Localization

If you change the API name of the None status after enabling Appointment Bundling, you must refresh the cache. To refresh the cache, edit and save your Bundle Config or any bundle policy.

Optimization

A scheduled path in a record-triggered flow doesn’t always work with optimization when Enhanced Scheduling and Optimization is enabled. In this case, the optimization updates are done by the platform integration user who has a session-based permission set that isn't active during the scheduled path’s execution. To grant this user the necessary permission, clone the Field Service Integration permission set, disable the Session Activation Required option, and then save. Then assign this permission set to the platform integration user. You can add more permission sets to this user if it’s necessary.

Propagation policies

Custom fields for service appointments used in aggregation policies must have read and edit access. See Create an Appointment Bundle Propagation Policy.

Recordset filter criteria

Inactive recordset filter criteria aren’t supported. See Create Recordset Filter Criteria for Bundling Appointments.

Restriction policies

Custom fields for service appointments used in sort policies must have read access. See Create an Appointment Bundle Restriction Policy.

Scheduling

Bundles and bundle members can't be part of a complex work chain. See Create a Field Service Bundle Manually.

Service Appointments list view

The Bundle Information fields from the service appointment’s details can’t be selected to display in a list view. See Create a Field Service Bundle Manually and Test Your Appointment Bundling Configuration.

Sort policies

Custom fields for service appointments used in sort policies must have read access. See Create an Appointment Bundle Sort Policy.

Travel time

• Travel time between the bundle member service appointments is also affected by the service resource’s efficiency.
• When you unbundle a bundle that includes travel time, the line that indicates travel between service appointments doesn’t appear on the Gantt.

See Create an Appointment Bundle Config.