--- schema_version: "1" id: edb412665e54cf631bc4c57b0d135687f53be3b3340183b2e54a0ee720e12738 title: Move to Lightning Data Service for Field Service Mobile collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/mfs_lightning_data_service.md canonical_url: https://help.salesforce.com/s/articleView?id=service.mfs_lightning_data_service.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 84fc3ea420fa631f8f4792af8c0c62a61aa3ee03fd6c833f37064fd74f617247 description: Lightning Data Service is an updated technology within the Field Service mobile app. Together with Lightning Web Components (LWCs), you get a powerful way to customize the app and use its latest features, all through using a simple setup. products: - Field Service release: "264" --- # Move to Lightning Data Service for Field Service Mobile Lightning Data Service is an updated technology within the Field Service mobile app. Together with Lightning Web Components (LWCs), you get a powerful way to customize the app and use its latest features, all through using a simple setup. ### Required Editions
Available in:  Lightning Experience in Enterprise, Unlimited, and Developer Editions.
Lightning Data Service is a caching mechanism crucial for loading and displaying LWC components and new features in the app. We redesigned the app's architecture around this unified cache that powers all app experiences. To access the new architecture and features, you must enable the Lightning Data Service permission set, or enable it when you set up your org, even if you don't plan to create your own LWCs. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_note.png) Note Lightning Data Service is enabled by default for all new orgs and sandboxes starting Winter ‘25. All orgs will be auto-migrated to Lightning Data Service by Spring ‘26. We recommend customers begin preparations and testing as soon as feasible. ## Get Started To take advantage of all ‌Lightning Data Service has to offer, complete the steps in either of these options. User Level Permissions To access Lightning Data Service, users need to have Lightning Web Components enabled. Follow the steps in [Define a Permission Set for Your Org](https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/sfs_gs_lwc_action_org_setup.htm#sfs_gs_lwc_action_org_setup) and [Assign the Permission Set to a Mobile User](https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/sfs_gs_lwc_action_org_setup.htm#sfs_gs_lwc_action_org_setup). Org-Wide Enablement Enable Lightning Data Service for your entire org in Field Service Settings. From Setup, in the Quick Find box, enter and select **Field Service Settings**. Under Lightning SDK for Field Service Mobile, select **Enable Lightning SDK for Field Service Mobile**. ## Learn About the Benefits, Preparations, and Changes with Lightning Data Service Lightning Data Service has many benefits and many Field Service features depend on its enablement, including AI features and Data Capture. ## Key Benefits These Field Service features are available only with Lightning Data Service. - [Data Capture](https://help.salesforce.com/s/articleView?language=en_US&id=sf.mfs_data_capture_about.htm): Use dynamic forms with field-level rules, branching logic, and custom UI support to streamline data collection in the field. Develop these forms quickly and easily in Flow Builder. - AI features: - [Pre-Work Brief](https://help.salesforce.com/s/articleView?id=service.mfs_einstein_pre_work_brief.htm&language=en_US): Get a concise overview of the tasks at hand, with customizable prompts to fit your work processes. - [Agentforce](https://help.salesforce.com/s/articleView?id=ai.copilot_intro.htm&language=en_US): Add a conversational AI assistant to the Field Service app to boost productivity, reduce service times, and improve first-time fix rates. - [Document Builder](https://help.salesforce.com/s/articleView?id=service.fs_document_builder_about.htm&language=en_US): Create richly formatted and branded PDF service documents, translate them, collect signatures, embed images, and generate previews on the desktop site and the mobile app. - LWC extensibility: Customize actions and create custom LWC tabs. - Tab navigation customization: Add new list views and tailor tab navigation. - Global search: Configure a new LWC tab in custom navigation to search against any object in the local cache, making it easy to find items in one place. - Revenue generation: Use a flow template that guides mobile workers through creating leads and opportunities from the app, without contacting customer services. - Performance and experience improvements: See [Lightning Data Service](https://developer.salesforce.com/docs/platform/lwc/guide/data-ui-api.html). ## Recommended Preparation Lightning Data Service has many benefits, but you can expect some changes to the app after you enable the Lightning Data Service permission set. These changes can affect your preexisting Flow customizations. Be prepared to do additional testing and tweaking to some parts of the app that use Flows and data priming for offline use. Make sure you’re ready for Lightning Data Service to achieve optimal performance. - Check device requirements: As we add more advanced features and scale the app for offline use, we recommend using the devices listed in [Field Service Mobile App Requirements](https://help.salesforce.com/s/articleView?id=service.mfs_requirements.htm&release=264.0.0&type=5 "Optimize your Field Service mobile app by following these technical specifications for peak performance and stability. These recommendations ensure prolonged usability and prevent common mobile device issues for organizations managing large mobile fleets."). - Review flow and priming changes: In some cases, small adjustments to your flows and priming strategy are necessary. - We recommend that you avoid flows on the Field Service mobile app that rely on Apex or record triggers. Record operations are routed through the Lightning Data Service draft queue, which is frequently processed in the background. How often it runs depends on a variety of factors, including available system resources. We cannot guarantee that the draft queue is processed instantly. - Avoid depending on fields during flow execution that are updated by non-mobile sources. - We recommend that you retest all of your flows. By doing this work in a sandbox environment, you can prepare your Field Service configuration for the latest app features. Also, review the flows section in [Field Service Mobile App Considerations](https://help.salesforce.com/s/articleView?id=service.mfs_limits.htm&release=264.0.0&type=5 "Review limitations and considerations for the Field Service mobile app for Android and iOS.") and [Offline Considerations](https://help.salesforce.com/s/articleView?id=service.mfs_offline_considerations.htm&release=264.0.0&type=5 "Your field service workers’ productivity doesn't have to stop when there's no connectivity. Learn how to use the Field Service mobile app when offline.") to ensure your flows and priming strategies follow the recommendations and limitations. If your LWC data queries are set up correctly, data requested by global LWCs and LWCs on work order and service appointment records are automatically primed. See [Use the Wire Service to Get Data](https://developer.salesforce.com/docs/platform/lwc/guide/data-wire-service.html). ## Developer Considerations - Avoid using Apex: Instead, use GraphQL (GQL) or the Lightning Data Service wire adapter. See [Use the Wire Service to Get Data](https://developer.salesforce.com/docs/platform/lwc/guide/data-wire-service.html). GQL updates data in the local cache, allowing LWCs to function offline. Remember, mobile connectivity isn’t always reliable, so GQL offers better performance in low-connectivity situations. ## Limitations Note these limitations when enabling Lightning Data Service. - Mobile Extension Toolkit (MET) isn’t supported.