Job Resource Bundles

Job resource bundles were introduced and standardized in FX26R1 to support consistent parent–child item handling across jobs, delivery tickets, and mobile workflows.

They are a parent–child grouping of job resource items on a job. The parent item and its children move together as a single unit—for example, when you add them to a delivery ticket or update their status.

Bundles let operations managers keep related items together so that partial shipments and status mismatches are avoided.

How Bundles are Created

You can create bundles in two ways:

From a Price Book or Quote: When you add a bundled Price Book Item (PBI) or Quote Item to a job with a quantity of n, the system automatically creates n separate bundles, each containing the parent item and its associated child items.
Dynamically on the job (FXL Bundle Maker): You can also create or modify bundles directly on the Job Resources grid by using the FXL Bundle Maker component. This lets you link a parent job resource with one or more child job resources, or add and remove children from an existing bundle.

Parent Job Resources

A parent job resource is any job resource whose associated Price Book Item has the FX5__Enable_Dynamic_Parenting__c field set to true.

The following rules apply to parent items:

The quantity of a parent job resource is always 1 and cannot be changed.

If you need multiple identical bundles, add the bundled PBI or Quote Item with the desired quantity; the system creates one bundle per unit.
A parent can have any number of child job resources linked to it

To preserve bundle relationships on Mobile Field Tickets, ensure the FX5__ParentJobResource__c field is included in sync configuration.

Status Behavior for Service and Labor Bundles

When a parent job resource has an Item Type of Service or Labor, the system automatically sets the parent status to On Site when it is created on a job.

All child job resources in the same bundle inherit this behavior:

When the parent status is set to On Site, every child in the bundle is also set to On Site automatically.
If a child item is itself of type Service or Labor, it follows the parent’s status regardless of its own item type.

This keeps parent and child statuses in sync and prevents downstream issues with delivery tickets, mobile workflows, and status-driven processing.

Bundles and Delivery Tickets

Job resource bundles are enforced as indivisible units on delivery tickets.

The following rules apply:

You can add a bundle to a delivery ticket only as a whole—parent and all children together.
- You cannot split a bundle across multiple delivery tickets
In the Create Delivery Ticket dialog, only the parent bundle item is shown for selection; child items are included automatically when the ticket is created
When the ticket is created, items are generated for both the parent and all child job resources in the bundle
Labor and Service job resources are not included as delivery-ticket items when generating a delivery ticket from a bundle

All generated delivery-ticket items (parent and children) include a link to the originating Job Resource.

Known Limitations

Serialized assets and serialized consumables: If a bundled Price Book Item or Quote Item includes a serialized asset or serialized consumable with a quantity greater than 1, the system does not create separate child items for each individual serial number. This is a current system limitation.

Admin Tasks

These are all configuration steps that only an admin would perform:

Enable Dynamic Parenting on Price Book Items
Set FX5__Enable_Dynamic_Parenting__c to true on any Price Book Item that should serve as a bundle parent. Also used on the Quote Item object as FX5__PBI_Enable_Dynamic_Parenting__c and Ticket Item object as FX5__PBI_Enable_Dynamic_Parenting__c. This is the core flag that drives all bundle behavior.
Structure parent–child relationships in Price Books
Build the parent-child PBI hierarchy so that when a user adds a bundle from a Price Book or Quote with quantity = n, the system auto-creates n bundles with children.
FXL Bundle Maker component setup
Drop the FXL Bundle Maker onto the appropriate Lightning record page via App Builder and configure search fields. The existing setup doc covers Tickets, Quotes, Invoices, and Price Books — but not FX5__Job_Resource__c yet.
Enable Drag and Drop for Bundle Maker
A one-time toggle in Lightning App Builder (Enable Drag and Drop BundleMaker on the FXL Data Grid v2). Already documented for other objects, but may need a note for the Job Resource context.
Serialized asset/consumable limitation
Admins need to know that if a PBI bundle has a serialized asset or serialized consumable with quantity > 1, the system will not create separate child items for each. This is called out in the epic description as a known limitation to document.