Work with Performance Priming in the Field Service Mobile App

What Performance Priming Does for You and Your Mobile Team

• Every change that Performance Priming supports syncs at least every 24 hours. Important changes sync about every 5 minutes. This means mobile workers pull a manual sync less often.
• A briefcase is the set of records and metadata downloaded for offline work. Performance Priming creates these briefcases for you from the profiles and data you select.
• Performance Priming gives mobile workers the capability to take a larger set of records offline, including the related records for the appointment in front of them.
• Performance Priming lets you tailor the priming logic to meet your own use cases; prime only the data and metadata your mobile workers need.

Prerequisites

• Performance Priming is available in Winter '26 and later, in production and sandbox orgs.
• Use Field Service mobile app version 264 or later from the App Store or Google Play.

General Considerations

• Performance Priming creates briefcases for up to 50 profiles that have the Field Service Mobile license on active users. Include the profiles that do field work.
• An auto-generated briefcase primes up to 100,000 records for each user.
• An auto-generated briefcase supports up to 1,000 rules. Complex page layouts can stop priming before every related-record level is included. Salesforce notifies admins and shows a warning on the generated briefcase.
• Briefcases include up to 2,000 service appointments.
• Offline priming runs in the Field Service mobile app. The same offline behavior isn't available in a browser on a phone or a desktop.
• The Field Service mobile app doesn't have a reliable way to detect online or offline status, as connectivity can change frequently and mobile signals are often unreliable. Our goal is to make sure that the app functions effectively offline first.
• Priming includes the metadata that makes those records usable offline: object and field definitions, page layouts, quick actions, and flow metadata.
• During priming, mobile workers can use the device for other work. On iOS, record downloads sometimes start after a short delay.
• When many mobile workers simultaneously onboard for an initial or full reprime on Performance Priming, the app may face priming delays.
• Each briefcase rule supports up to 75,000 records. To raise that limit, contact Salesforce about a High Volume Briefcase.
• An object supports up to 10 fields across filters and relationships in briefcase rules. Each way you slice the work uses one of those fields. For example:
  • Service appointments the mobile worker owns (Owner ID)
  • Service appointments in the past 7 days or the next 7 days (scheduled date)
  • Service appointments in a bundle (related bundle ID)

  Those three jobs use three fields. Seven fields remain for other filters and relationships on that object.

• We prime all lookup relationships up to three levels deep. For example: Consider a user with 10 service appointments, each linked to a parent work order. Each work order has a related list containing 3,000 work order line items.
  • The 10 service appointments and their 10 corresponding work orders are primed.
  • For the work order line items, the first 2,000 items from each of the initial 5 work orders are primed. This totals 10,000 records, which meets the overall related list limit.

Schedule Changes During the Shift

Dispatchers change appointments throughout the day. The mobile worker gets a text notification for a new or updated appointment.

• If the app is open or in the background, the service appointment primes when the notification arrives.
• If the app isn't running, the appointment and its related records prime after the worker opens the app and taps the notification. On iOS, the mobile worker taps the notification to prime it.

Data Refreshes

Workers see two update speeds. Supported changes arrive about every 5 minutes. Everything else that Performance Priming covers arrives at least every 24 hours. A delta sync downloads changes since the last sync, not the full briefcase.

Change Data Capture

• Objects that support Change Data Capture can use the faster delta sync. Objects that don't support it refresh every 24 hours. To see which objects qualify, in Setup, go to Integrations and then Change Data Capture. An object that isn't listed refreshes on the 24-hour cycle.

Delta Priming Delays

Future appointments and service document templates can take up to 24 hours to enter the briefcase. Performance Priming rechecks existing records every 24 hours. New records are checked right away through Change Data Capture.

Example: You prime service appointments up to 7 days ahead.

• An appointment 7.1 days out is outside the window, so it isn't primed yet.
• At the next daily check, that appointment is 6.1 days out. It matches the filter and is primed.
• An appointment can sit inside the window for part of a day before it downloads. For a 2-day window, an appointment is primed when it is 1.1 days away.

The same delay applies to Future Days in the Date Picker and Days After Current Service Date in Field Service Mobile Settings. Tell dispatchers that a newly in-range appointment can arrive on the next daily check rather than the moment it crosses the window.

Lists That Stay Stale Until Refresh

• Some lists on the device don't redraw when a delta sync finishes. The records are already on the device. The worker updates the list by pulling to refresh, online or offline. Call this out in training so a worker doesn't treat an old list as the current schedule.
• Custom tabs and the Profile Absence list follow this pattern.
• A record deleted in Salesforce can remain on the mobile list until the worker pulls to refresh.
• To change a list view that a briefcase rule uses, clone the list view and edit the clone. Then select the clone in Field Service Mobile Settings. Edits to the original list view are rejected after Performance Priming is on.

App Builder List Views

• List views from App Builder aren't part of the automatic briefcase. Workers download them with Sync. If a team depends on one of these lists in the field, include Sync in their start-of-day routine.

Resource Absences

• A new or removed resource absence doesn't update the Resource Absences list on the Profile tab after delta priming. The worker pulls to refresh before relying on that list for time off.

Unsupported Objects

• Briefcases don't include asset attributes, milestones, or asset types. Mobile workers will need a network connection when the job depends on those records.

Error Reporting

• The app doesn't show an error for each record or metadata item that fails to prime. Before a broad rollout, sign in as a mobile worker and confirm the appointments, work orders, and related records you expect are on the device.