Set Up Job Resource Bundles

Before users can work with job resource bundles, an administrator must complete the configuration steps below.

Before You Begin

  • You need System Administrator access to the Salesforce org

  • You need edit access to Lightning record pages in Lightning App Builder

  • Familiarize yourself with the Job Resource Bundles concept topic

  • Users must have create and edit permissions on Job Resource (FX5__Job_Resource__c) to manage bundles

1. Enable Dynamic Parenting on Price Book Items

The Enable Dynamic Parenting field (FX5__Enable_Dynamic_Parenting__c) on the Price Book Item (FX5__Price_Book_Item__c) object controls whether an item can act as a bundle parent.

  1. Open the Price Book Item record that will serve as a bundle parent.

  2. Set Enable Dynamic Parenting (FX5__Enable_Dynamic_Parenting__c) to true.

  3. Save the record.

  4. Repeat this process for each PBI that will act as a bundle parent.

2. Structure Parent–Child Relationships in Price Books

Bundle children are determined by the parent–child hierarchy defined in the Price Book.

  1. In the Price Book, create or edit the parent PBI (the one with FX5__Enable_Dynamic_Parenting__c = true).

  2. Add the child PBIs beneath it using the standard Price Book Item hierarchy.

  3. Verify that child PBIs appear under the correct parent in the Price Book Item hierarchy.

When bundles are created from a Quote, the system applies the same parent–child hierarchy defined in the Price Book. This ensures that bundle structures remain consistent between Quotes and Jobs, so users see the same parent and child items regardless of where the bundle originates.

3. Configure the FXL Bundle Maker component

The FXL Bundle Maker lets users dynamically add or remove children from a bundle on the Job Resource record page.

  1. Open Lightning App Builder and edit the Job Resource record page.

  2. Drag the FXL Bundle Maker component onto the page layout.

  3. Configure the search fields for the component:

    1. In the component properties panel, locate the search field configuration settings.

    2. Select the fields that users will search on when adding child Price Book Items (for example, Name, Item Number, or other identifying fields).

    3. Save the configuration.

    4. Verify that users can search for and select child items in the FXL Bundle Maker component on the Job Resource record page.

  4. If the FXL Data Grid v2 component is present on the page, enable Drag and Drop Bundle Maker to allow users to rearrange bundle items.

  5. Save and activate the page.

    If bundle children do not appear in the FXL Bundle Maker:

    UI configuration

    • The component is present on the active Job Resource Lightning page

    • The page is assigned to the correct app and profile

    Data configuration

    • Parent and child Price Book Items exist in the active Price Book

    • The parent PBI has FX5__Enable_Dynamic_Parenting__c set to true

    Sync configuration (mobile and profile-driven behavior)

    • The field FX5__PBI_Enable_Dynamic_Parenting__c is included in the sync profile

    After correcting configuration, refresh the page or re-sync and confirm that bundle children are available.

For detailed component configuration, see Setup for the FXL Bundle Maker component.

4. Verify Profiles include the Parenting Field on Ticket Items

On the Ticket Item (FX5__Ticket_Item__c) object, the parenting flag is surfaced as a derived field named FX5__PBI_Enable_Dynamic_Parenting__c.

Profiles that are missing this field — particularly profiles generated by the Sync Profile Manager Admin tool — will remove the Add button for child items after a sync.

  1. Open each relevant profile (especially the Sync Profile Manager Admin tool-generated profiles).

  2. Confirm that the field FX5__PBI_Enable_Dynamic_Parenting__c is included in the field-level security for FX5__Ticket_Item__c.

  3. If missing, add the field and save the profile.

5. Understand Bundle Creation Behavior

When a user adds a PBI configured for dynamic parenting to a job with a quantity greater than 1, the system creates one bundle per unit.

After Configuration

FieldFX Mobile App Considerations

For bundles to work correctly,

Mobile App Validation Checklist - Click to expand

FieldFX Mobile App Validation Checklist

Use this checklist to verify that required data and configuration are available in the mobile app and that feature behavior matches expected results.

Step Requirement Test Expected Result Failure Symptoms

1. Price Book Items Available in Sync

Parent and child Price Book Items must be included in the sync profile.

  1. Open the mobile app and navigate to the relevant record.

  2. Use the search function to locate a parent Price Book Item configured for dynamic parenting.

  3. Add the item.

  • The parent Price Book Item appears in search

  • Related child items are created based on the configured hierarchy

  • The parent Price Book Item does not appear in search.

  • The parent is added, but no child items are created.

2. Required Fields Included in Sync

Required fields used for feature behavior must be included in the sync profile (for example, FX5__PBI_Enable_Dynamic_Parenting__c).

  1. Add a parent item to the record.

  2. Attempt to view or manage related child items.

  • Controls for managing related items (such as Add) are available.

  • Users can view or modify related items.

  • Required controls (such as Add) are not visible.

  • Users cannot view or manage related items after sync.

3. Parent Configuration Valid

The parent record must be configured to support hierarchical behavior (for example, FX5__Enable_Dynamic_Parenting__c set to true).

  1. Add the parent item in the mobile app.

  2. Observe system behavior.

  • Related child items are created automatically.

  • The parent item is added without related child items.

4. Bundle or Hierarchy Editing While Offline (Mobile Offline Validation)

  1. Put the mobile device in offline mode.

  2. Open a record that contains related items.

  3. Attempt to:

    • Add a related item

    • Remove a related item

    • Reorder items (if supported)

  • Existing related items are visible.

  • Controls to modify related items (such as Add or drag-and-drop) are unavailable or disabled.

If required data or fields are not included in the sync profile, feature behavior may be partially or fully unavailable in the mobile app.

Automatic Behaviors (No Configuration Required)

The platform automatically applies the following behaviors. No setup is required.

Service and Labor Status Sync

When a parent job resource has Item Type = Service or Labor, the system automatically sets its status to On Site upon creation. All child job resources in the bundle inherit this status automatically.

This keeps parent and children in sync and applies whether the Service or Labor item is the parent or a child.

Delivery-Ticket Bundle Rules

  • Bundles are indivisible — you cannot split a bundle across multiple delivery tickets

  • The delivery-ticket dialog shows only the parent; children are included automatically

  • Labor and Service items are excluded from the delivery-ticket dialog

  • Each child delivery-ticket item retains a job resource link back to its originating job resource record.

Known Limitations

Serialized assets and consumables

If a PBI bundle contains a serialized asset or serialized consumable with quantity > 1, the system will not create a separate child item for each serial number. Communicate this limitation to users who work with serialized inventory.