Manage the Field Service mobile app
Manage the Field Service mobile app
This domain tests configuration and support of the model-driven Field Service mobile app used by technicians, especially offline and device scenarios.
Core rules and concepts
- The Field Service mobile app is a model-driven Power App. Control access with security roles and app module assignments.
- Mobile offline profiles define which tables and records sync to devices. Filters should be narrow enough to sync quickly but broad enough for the technician's day.
- Technicians work with bookings, work orders, service tasks, products, attachments, notes, inspections, and signatures.
- Device features can include barcode scanning, location capture, camera attachments, and time tracking, depending on app configuration.
- Offline changes sync when connectivity returns; conflicts and sync errors must be monitored.
- Publish app changes and test on a device with a realistic offline profile before broad deployment.
Worked example
A technician works in a basement with no signal. The offline profile syncs today's bookings, related work orders, service tasks, and customer assets. The technician completes tasks, captures a signature, and records used parts. When connectivity returns, the app uploads changes. The reasoning is that offline filters must include the records needed to complete work, not just the booking record.
Traps that cost marks
- Creating an offline filter so broad that devices sync excessive data and time out.
- Forgetting that related records such as tasks and products may need their own offline inclusion.
- Testing only online; offline behavior differs.
- Missing security role or app access, so the user cannot open the app.
- Assuming sync conflicts resolve silently; they require monitoring and correction.