Loading
Salesforce から送信されるメールは、承認済ドメインからのみとなります続きを読む

Salesforce Field Service app for iOS and Android performance considerations

公開日: Sep 12, 2025
説明


Caching Settings and Priming Implications

In general the repriming and update behaviors in, the Salesforce Field Service mobile app are impacted by a number of Field Service Mobile Settings.

The main settings that control the behavior are:
  • Schedule Update Frequency Time in Minutes - Controls the number of minutes between attempts to update a user’s schedule. This setting could contribute to extra downloads and data usage. Consider setting the value to the highest value possible.
  • Record Data Cache Time in Minutes - Controls how often priming occurs and the number of minutes that record data is kept in the app’s local cache. This controls how long offline data is considered valid for. When this time expires, the app will check for updates on the next sync or when the record is accessed. When this setting is a low value, it could cause excess network usage and reduce performance.
  • Metadata Cache Time in Days - Controls the number of days that org metadata, such as layouts, is kept in the app’s local cache.
解決策


    Considerations to Improve Sync Times

    The time for priming to complete can vary widely depending on the amount of data primed. You can adjust settings to ensure the app primes quickly. These adjustments benefit performance, battery life, and network usage.

    Priming starts by loading all Service Appointments for the default list view. We recommend having this set to only include the data needed for technicians in the field.
    • Note: If you are syncing several hundred records in your default list view, you can expect the sync to take a significant amount of time and affect performance.
     

    If using the built-in list view (no value set in Salesforce Field Service mobile settings for 'Default List View Developer Name'):

    1. Ensure your 'Future Days Date Picker' and 'Past Days in the Date Picker' are set to the minimum value needed for technicians to be productive. Any appointments assigned to resources that occur between these dates are pulled down and synced at login. 
    2. If possible consider using a custom list view for offline data and primary use cases and an alternate list view if users may need to occasionally see other values.


    If using a custom list view (Specified in Salesforce Field Service mobile settings 'Default List View Developer Name'):

    1. Status: If users do not care about Service Appointments in certain states, consider excluding them from the List View. For example, Closed Service Appointments may not need to appear in the users' primary List View.
    2. Scheduled Start: Users may not need to access appointments that occurred a long time in the past. Consider something like SCHEDULED_START GREATER OR EQUAL TO LAST 7 DAYS or similar.
    3. Scheduled End: Users may not need to access appointments far in the future. Consider something like SCHEDULED_END LESS OR EQUAL TO NEXT 7 DAYS or similar.
    ナレッジ記事番号

    000380155

     
    読み込み中
    Salesforce Help | Article