Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

Record-Triggered Flows do not execute on child records during cascade deletion in Field Service

Publish Date: Jun 12, 2026
Description
Problem

When opening a Data Capture form in the Field Service mobile app Forms tab, the form hangs on a loading spinner or displays a generic Something went wrong error. Form fields and layout do not render. The issue occurs consistently for the same form or record type, even after closing and reopening the app.


Cause

When a Data Capture form opens, the Lightning Data Service (LDS) and LWC framework must retrieve form layout metadata and field definitions from the org. Initialization fails when:

  • The Field Service Integration permission set lacks Read or Edit access on custom fields mapped in Data Capture flows
  • A validation rule or lookup filter on the Service Appointment or Work Order object blocks the framework from querying or rendering the form structure
  • The briefcase configuration is incomplete or missing required entities needed for offline form initialization
  • Cached metadata on the mobile device is stale and conflicts with the current org configuration
 
Resolution
Follow the steps below in order to restore form loading.

Step 1: Verify Field-Level Access on the Field Service Integration Permission Set

  1. Go to Setup → Permission Sets and select Field Service Integration
  2. Click Object Settings and choose the target object (Service Appointments or Work Orders)
  3. For each custom field mapped in your Data Capture flows, confirm both Read Access and Edit Access are checked
  4. Save your changes


Step 2: Deactivate Restrictive Validation Rules and Lookup Filters

  1. Go to Setup → Object Manager and select the target object (Service Appointment or Work Order)
  2. Click Validation Rules and review any rules that reference fields used in your Data Capture form
  3. Temporarily deactivate any rule that may interfere with form initialization (for example, rules that fire on record load or reference lookup fields)
  4. Repeat for Lookup Filters on the same object
  5. Test the form in the mobile app. If the form loads, re-enable rules one at a time to identify the specific rule causing the issue, then refine its logic to exclude the form initialization context
 
NOTE: Validation rules may be required for data integrity in other contexts. Avoid deactivating them globally — refine the rule logic to exclude form initialization, or use a custom field flag to bypass the rule during Data Capture form rendering.


Step 3: Verify Briefcase Priming Configuration

  1. Go to Setup → Briefcase Priming Configuration (or Briefcase Builder, depending on your org version)
  2. Confirm that all entities required for your Data Capture forms are included — typically Service Appointments, Work Orders, and any related custom objects
  3. Verify that all custom fields referenced in your form mappings are included
  4. Save changes and trigger a briefcase sync on the mobile device

NOTE: Briefcase configuration changes may take several minutes to propagate to mobile devices. Allow time for the sync to complete before retesting.


Step 4: Clear Cached Metadata on the Mobile Device

  1. Open the Field Service mobile app
  2. Navigate to Settings or the app menu
  3. Select Clear Cache or Clear Offline Data (exact label varies by OS and app version)
  4. Confirm the action and allow the app to re-sync metadata from the org
  5. Return to the Forms tab and attempt to load the form again


NOTE: Cache-clearing options vary by device OS (iOS vs. Android) and Field Service mobile app version. Consult your device's app settings or mobile app documentation for precise steps.
Knowledge Article Number

005386922

 
Loading
Salesforce Help | Article