Best practices and limitations for the offline profile
Field technicians often need to work in areas without Internet access, like remote places or underground. When an admin sets up the Field Service mobile offline profile, technicians can continue using the mobile app when there's no Internet connection. Important data syncs to the device for viewing in the field. Changes on the device are stored locally, and then uploaded automatically when an Internet connection becomes available.
Read our blog post about best practices for offline mode.
Even if you think your field technicians will always have a reliable Internet connection, we strongly recommend that you set up offline capabilities to create a fast and consistent experience.
The offline profile manages offline record types, relationships, and user assignments. For a guided walkthrough, watch this brief video.
The Field Service mobile app follows the same architecture and security as a Power Apps mobile app. Learn more about Power Platform security.
Best practices for using the offline profile
Before you set up the offline profile, consider these important guidelines:
Use the default offline profile. Although you can create your own mobile offline profile, we highly recommend that using the default offline profile provided by Field Service. The Field Service Mobile - Offline Profile provides an ideal starting point for offline scenarios. It has common Field Service tables preconfigured for offline use, and recommended filters to limit the data that gets downloaded. Build on it by including your custom record types. Make sure to limit the amount of data you include in the offline profile for the best sync performance.
The default offline profile receives updates to unchanged table sync filters. You can copy the default profile and make changes to the copy, but the copy is unmanaged and doesn't receive any updates.
If you make changes to the default offline profile and want to see the latest offline profile later, create a new trial of Field Service.
Don't remove default record types from the offline profile. We purposefully added default record types to make sure that the right data is available to field technicians. Focus on adding the record types you need rather than removing ones you don't.
Don't use "All records" as an offline filter. The offline profile is the gate that controls the amount of data to download to users' devices. Technically, there's no limit to the number of records the offline profile supports. Practically, however, the less data that gets downloaded the faster and more efficient syncing is. Don't use "All records" as a table filter, and avoid wide date ranges. For example, rather than downloading all customer asset records, download only the records that are related to scheduled work orders. It reduces the number of customer asset records that need to be synced without affecting the work at hand.
Use offline JavaScript. Organizations often need to run workflows on mobile devices to execute business processes. However, Power Automate flows only run when the device has a network connection or on the next sync. If you need to run workflows on the device on-demand and without Internet access, use offline JavaScript instead. Learn more about workflows and scripts for the Field Service mobile app.
Learn more best practices for using mobile apps offline.
Limitations of the offline profile
Keep these limitations in mind when you set up the offline profile:
Field Mapping isn't supported in offline mode.
Records that are created on the device in offline mode and don't meet filter conditions aren't synced until they meet the conditions.
Make sure that commands or capabilities that are set up for Internet connectivity call the correct APIs:
Xrm.WebApi.online.Tables that support offline use are part of the default Field Service Mobile - Offline Profile. You can add tables to the offline profile, but some, such as Purchase Order, Agreements, return to vendor (RTV), and return merchandise authorization (RMA), can't be used offline. If you add these tables and run the app offline, users might get errors.
The Field Service Mobile - Offline Profile can have a maximum of 15 linked tables, including downstream tables. For example, if Table A has a relationship with Tables B, C, and D and Table B has a relationship with Tables F, G, and H, then Table A has six relationships: B, C, D, F, G, and H. Add Table J with a relationship to table K and no relationship with any other table, then the total number of linked tables is seven. Learn more about profile filter limitations.
Inventory validation doesn't run without network connectivity.
Access to SharePoint documents isn't supported.
Access to knowledge articles isn't available in offline mode.
Web resources are partially supported in offline mode. We recommend that you use the Power Apps component framework to implement custom capabilities that work in both the mobile app and the browser.
The Export to PDF option isn't available while the application is in offline mode. Other options might be hidden while in offline mode or without device connectivity. Learn more: Ribbon and Command Bar Button is Hidden.
Data reducution checklist
To reduce the amount of data the mobile app uses, consider the following actions:
- Limit customization. To understand how customizations are consuming data, use debugging tools like F12 in the browser or Fiddler with the Windows app.
- Create an offline profile and enable offline-first mode. Make sure business can be performed offline and large synchronizations can be handled over Wi-Fi.
- Limit views and forms to the minimum required.
- Use default views that filter data to only the data that's important to the field worker. For example, my recent bookings instead of all bookings.
- Allow image resolution to default to smaller file sizes for photo capture.
- Review other performance considerations for customizing the mobile app.