--- schema_version: "1" id: 4b8fa83375ef3062c49a7d1817c12303e58f650d4fc41d5bcfeb1db1fda8b036 title: Field Service Mobile App Limitations for Workforce Scheduling collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/wfs_mobile_app_limitations.md canonical_url: https://help.salesforce.com/s/articleView?id=service.wfs_mobile_app_limitations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: d3d1e0d67687d6c2a7da8a5342ffe5ad9fa579d2c05a378983001a3d75f7b35f description: Review constraints for barcode scanning, inventory, knowledge, appointments, and work orders in the Field Service mobile app. products: - Public Sector - Service Cloud release: "264" --- # Field Service Mobile App Limitations for Workforce Scheduling Review constraints for barcode scanning, inventory, knowledge, appointments, and work orders in the Field Service mobile app. ### Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions
To access the Field Service mobile app, users need the Field Service Mobile user license.
## Barcode Scanner - For a list of supported barcodes, see [Supported Barcodes](https://help.salesforce.com/s/articleView?id=service.mfs_supported_barcodes.htm&type=5&language=en_US). - (iPad) Barcode scanning isn’t supported in Split View. ## Briefcase Builder - Related lists don't work offline when the records are primed with Briefcase Builder. - The Product object in the Inventory tab isn’t supported. - The **Inventory** tab isn’t available offline. - Briefcase configuration for Public Sector Solutions data is an unmanaged package. ## Chatter - The Feed tab in iOS is supported only on the work order, work order line item, service appointment, and case objects. The Feed tab in Android is supported only on the work order, work order line item, and service appointment objects. - (Android only) Chatter is disabled when the app doesn’t have internet connectivity. ## Data Capture - You can add Create, Update, or Delete operations only at the end of the flow. You can't add screens after or between any Create, Update, or Delete operations. Create, Update, and Delete operations can be in any order, as long as they're all at the end of the flow. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-workforce_scheduling-264-0-0-production-enus/1eb114f2-bdf8-40c9-98ed-accb880f7906/images/icon_note.png) Note This constraint protects offline integrity. Create, Update, and Delete operations run only while a mobile worker is online. When a mobile worker is offline, these operations wait until the mobile worker is online again. - Create Records, Get Records, Update Records, and Delete Records operations can retrieve only records of User Interface API enabled objects. For the list of supported objects, see [All Supported Objects](https://developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/ui_api_all_supported_objects.htm). - Subflows are supported, but you can't use Create, Update, or Delete operations with them. - Data Capture forms aren't supported for interactions. ## Interactions - Data Capture forms and service documents aren't supported for interactions. ## Inventory Management - If you use the **Enable Multiple Locations** setting, the **Add** and **Add All** buttons are removed from the Product Required screen. Manually add the required products for multiple inventory locations. - When you use multiple inventory locations, a maximum of 10 locations per location type are shown and primed. - A maximum of 1,000 products are shown in inventory lists. That number is also the maximum number of products that can be primed. - When a mobile worker consumes a serialized product in the Field Service mobile app, the app creates a product consumed record without serial numbers. Mobile users can delete those records only if they have delete permission on Products Consumed. - If a work order includes serialized products as required items, you can view the required products, but the **Add All Products Required** button is unavailable. - Only users with an admin profile can delete product consumed records for serialized products. ## Knowledge - (iOS only) If images in knowledge articles are hosted outside of Salesforce, they display normally. Images uploaded to Salesforce don’t load correctly. Use an image link that users can open. You can avoid this issue by selecting the option to use POST requests for cross-domain sessions. Find this option on the **Session Settings** page in Setup. - (iOS only) Some knowledge articles in supported languages, such as Japanese, don't show in the Field Service mobile app. - (Android only) The Knowledge Article action isn’t visible on the Work Order Overview screen. View knowledge articles from the related list. - (Android only) In knowledge article details, field names such as Title don’t display on Android devices. - If a device is running in any of Salesforce’s 26 supported languages, the app translates knowledge articles to that language. If the device isn’t running in a supported language, no knowledge articles are shown. - Settings for optimized images are supported in files uploaded in mobile flows. Those settings aren’t applied to images uploaded in the Chatter feed. - (iOS only) If a knowledge article is updated on the desktop site, users must log out and log back in to the Field Service mobile app to see the changes. ## Pre-Work Brief - Pre-Work Brief requires additional licensing and isn't available to all customers. The Pre-Work Brief template is available for Licensing, Permitting, and Inspections (LPI) use cases only, with Business License as the assumed Visit parent. ## Lightning App Extensions - The Salesforce mobile app can launch and accept parameters for Visualforce pages exposed as a Lightning page tab. The Lightning page tab name can’t include spaces. ## Lightning Web Components - Lightning web components in the Field Service mobile app don't fetch picklist values during priming. As a result, Lightning web component page references aren’t primed. - Priming times when Salesforce Lightning Design System (SLDS) is enabled depend on the Lightning web components that are primed. Long priming times can come from Lightning web components that trigger numerous adapter calls during priming. - Service appointments and work orders aren't supported for Lightning web component quick actions. - Implement state saving in Lightning web component actions so users can do other work in the Field Service mobile app while an action is running. Without state saving, if users leave the action to do other work in the browser, Android devices reset the in-progress component's state. - Tabs that contain content, such as forms that use Lightning web components, can reset and lose their content. On iOS, this issue occurs when switching between Lightning web component tabs. On Android, it can happen when switching between any tab types and when rotating the device. ## Quick Actions - For Salesforce Lightning Data Service-enabled environments, global quick actions don’t refer to the record type fields. - Lightning component and custom override quick actions aren’t supported. - Quick action values aren’t updated when working offline. - Quick actions can override the Accurate Record Dates for Offline permission, which causes inaccurate logging after the app comes back online. - Custom icons in quick actions aren’t supported. - Quick actions with default values can take up to a minute to render during poor or unstable network connectivity. - Service appointments and work orders aren’t supported for Lightning web component quick actions. ## Related Lists - Data Cloud objects, including objects with `__dlm`, `__dll`, or CDP API names, aren't supported in related lists in the Field Service mobile app. - The Notes related list isn’t supported. - Related lists display up to 50 records because of performance concerns with GraphQL queries. You can override the 50-record limit with the `RELATED_LIST_LIMIT_OVERRIDES` custom app setting. - Related lists don’t show details of Salesforce objects that you can’t include in a page layout, such as Work Order History. - Related lists for person accounts don't work if the related list doesn't use Account as the lookup field. ## Resource Absences - If you haven’t primed or viewed any resource absences, you receive a network error when you try to create and view resource absences offline. ## Service Appointments - The Recently Viewed service appointments list view shows all service appointments assigned to a user, including appointments the user hasn’t viewed. - Service appointment list views of more than 2,000 records don't display labels in the dropdown menu on the **Schedule** tab. - The schedule list isn't refreshed until the `ScheduleUpdateFreq` timeout value is reached. - If you use Appointment Assistant, Appointment Assistant starts when a mobile worker updates the status of a service appointment by editing the record. It also starts when the appointment is updated through a flow or an automatic status change. When a Lightning web component updates the same status, Appointment Assistant doesn’t start. - The mobile app fetches a maximum of 1,000 service appointments from all service appointment list views. - When you view a service appointment from the desktop site, the `LastViewedDate` field is updated. - (Android only) When the **Subject** field on Service Appointment is null, the **Last Modified Date** field shows as the subject on Android devices. - Service appointment bundling isn't supported for service appointments that have a Visit or Interaction context record. - When a service appointment is associated with a Visit or Interaction, the actions menu uses the Visit or Interaction for record edit and record details. Contact actions, get directions, and status change use the service appointment. ## Work Orders - To sort work order line item records numerically, use this format. - Add a zero, if needed, to create a two-digit number. For example, 02 sorts before 12. - If you need 100 items or more, create a text field and add numeric values prepended by zeros to create a three-digit number. Then sort on that field. For example, 002 and 012 sort before 100. Field Service on the desktop site doesn’t support preceding zeros. To sort on the desktop site, define the sort order by 10 on a number field of a custom object, for example, 10, 20, and 30. - For the Overview tab to be visible, work order line item page layouts must include the Asset field and the Service Report related list. - Searching the price book fails if you assign rich text area fields to the Product object’s search layout. - Work orders allow a maximum of 1,000 work steps per work order. The total length of all fields on the Work Step object must not exceed 20,000 characters. If you exceed this limit, some work steps don’t appear in the mobile app. - If sharing isn't enabled for the Work Order object, work orders disappear from the search list view in the Work Order lookup after the user logs out of the Field Service mobile app. ## General Limitations - When the mobile app displays related lists, such as the work order line items for a work order, the number of records returned depends on the size of the object and the fields on that object. - Plain text fields don't support rich text or HTML content. - Time fields without a date aren’t supported in the Field Service mobile app. - Under the profile tab, only 10 resource absence records are displayed. - Visualforce pages aren’t supported in the app, including actions and Visualforce components on page layouts. - Lookup filters aren’t supported. - Enhanced notes aren’t supported. - Users can’t change the ownership of objects such as service appointments or work orders. - In some countries, mapping features such as driving directions and estimated time of arrival (ETA) aren’t supported for Apple Maps or Google Maps. - If a user’s device is offline, its location data can’t be accessed. When the device is back online, its last known location is sent to Salesforce. - The Contact Card section on the Work Order Overview screen displays the contact associated with the service appointment, rather than the work order. To view the Contact Card, populate the Contact field on the service appointment. - Paging isn’t supported for SOQL queries. The maximum number of records a query can return is 2,000. - Formulas aren’t supported on the Details tab. - If a default list view is selected, the app shows every list view that a user has access to. You can't hide a specific list view in the Field Service mobile app. - If a selected picklist value is inactive, it isn’t shown in the Field Service mobile app. The inactive value is shown on the Field Service desktop site. - If a launch field value passes a URL from a formula field, app extensions return an error that a required app isn’t installed. - If a currency field is updatable, it’s displayed as a number without a currency symbol and uses the field’s decimal places setting. If the currency field isn’t updatable, it’s displayed as a number with a currency symbol and two decimal places. - When a currency field supports multiple currencies, only the stored amount shows in the mobile app. Currency conversions aren’t displayed. - If the record type field isn’t on the page layout when a resource absence is created, the default record type is set. To set the record type yourself, add the Record Type field to the resource absence page layout. - User Profile on the User page and Record Type on the Work Order Details page aren’t supported as layout objects. They can appear as links in the Field Service mobile app. Selecting these links shows an error message and a blank screen. - Record pagination isn’t supported in the Field Service mobile app. - Notification settings use the mobile settings assigned to the user who starts the request, not the user who receives the request. - If an object hasn't been primed or previously accessed, including new records, it isn't visible from another object’s page. - When you launch the Field Service mobile app, the lock screen keeps the same screen orientation. Rotating the device doesn’t change that orientation. To change the lock screen orientation, close the mobile app, change to the orientation you want, and then relaunch the mobile app. - During OAuth 2.0 authentication, Salesforce creates a temporary short-term session to bridge the gap between login and the Salesforce authorization (Allow Access) screen. This temporary session, which uses a cookie, isn’t tied to the OAuth refresh or access token and therefore isn’t invalidated at logout. The session remains valid until it expires. The most recently authenticated user stays logged in until the temporary session expires, and during that time the user can’t log out. These sessions have a short lifetime. After the session expires, the user can log in normally. - In orgs with Salesforce Lightning Design System enabled, the Old Value and New Value field values can’t be loaded on history related records. - The Field Service mobile app doesn't support free-form text entries in picklists. - If a network error occurs, the Field Service mobile app can try to recreate a link from a record to a content document. That attempt returns the error message “Document with ID XXXX is already linked with the entity with ID YYYY.” This issue can also occur when uploading images in flows. To keep these error messages from showing, set the `DUPLICATE_AVOIDANCE` custom attribute to True. This issue occurs only when Lightning web components aren’t enabled. - Apps that use Experience containers aren't fully duplicated in Partial Copy, Developer Copy, or Developer Pro Copy sandboxes. Data is copied only in Full Copy sandboxes, and that data carries over to the Experience container. - Biometrics aren’t supported for the Field Service mobile app. Don’t add the Biometric custom attribute to the connected app. - Icons in the Field Service mobile app aren't customizable. - When you create a Partial Copy, Developer, or Developer Pro sandbox, only the metadata from the production org is copied. To copy both metadata and data, use a Full Copy sandbox. - You can backdate a record when you create it. You can't backdate a record when you update it. For the required permissions, see [Knowledge article 000386699](https://help.salesforce.com/s/articleView?id=000386699&type=1&language=en_US). - iOS devices stay awake during priming without the user tapping the screen. If Low Power Mode is on, the device doesn’t stay awake during priming. - Custom list views can take a minute or more to sync. - Only plain text is supported for rich text fields. - Default values aren’t available offline. - Lookup fields such as Account aren’t supported on the Schedule, Work Order, and Work Order Line Item tabs. - Custom overrides on actions aren’t supported, including custom overrides on lookup logic. - Apple limits what apps can do in the background or when the device is locked. Finish priming before the device goes offline. - On iOS, the Waze app works best when you use coordinates rather than addresses to specify a destination. - In iOS 14 and later, the Field Service mobile app doesn’t use the default app settings on the device. For example, if you choose Outlook or Gmail for email, Field Service uses the iOS Mail app. - Actions in landscape orientation aren’t supported. Actions are shown only in portrait orientation. - iOS has a 24-hour format setting that overrides other time settings, regardless of the device's region or locale. This format override affects components such as the date and time picker and flow fields. - You can’t copy and paste data from apps other than Salesforce, such as Safari, when `DISABLE_EXTERNAL_PASTE` is set to TRUE in the connected app settings. - In iOS 15, the iPad calendar view doesn’t show dots to indicate that a service appointment exists. - On iOS, an ETA and driving directions are provided only if the user is within 1,000 km of the destination. - On iOS, photos uploaded from the Field Service mobile app sometimes include extra white space. To prevent this issue, delete the `MAX_IMAGE_UPLOAD_SIZE` connected app setting. When you take landscape photos in the Field Service mobile app, make sure the device's camera orientation sensor is active. The sensor is active when the zoom factor buttons change their rotation. Tilting the device so the screen faces up from a portrait position, and then rotating it, can fail to trigger the orientation sensor.