Building on my earlier post, Dynamics 365 Field Service Mobile – Real World Performance Insights, which focused more on the hardware side, I wanted to share a few app-level optimisations that have genuinely helped improve Field Service Mobile performance in my recent deployments.
These are practical tweaks together, they do make a noticeable difference:
Microsoft FCB Patch Deployment:
Microsoft has released an FCB patch that partially addresses the infamous “circle of death” issue, particularly around Booking views. While not a complete fix, it does improve stability.
Reduce Records per Page:
Lowering the records per page to around 25 significantly improves scrolling performance in booking-related views on the mobile app.
Mobile Form Scripts:
Microsoft recommends removing unnecessary console.log statements from JavaScript used on mobile forms. This small clean-up can positively impact form load times.
Remove Unused Fields from Mobile Forms:
Keeping only the fields that technicians actually use helps reduce form load time—and these incremental gains add up across the app.
Remove Unused Columns from Views:
Following Microsoft best practices, trimming down unused columns in views reduces data load during navigation and improves overall responsiveness.
Optimise Mobile Offline Profile Filters:
Recent enhancements that allow limiting offline data to specific columns are a big win. When configured carefully, both at the table and related table levels this can dramatically reduce offline data size and improve offline performance.
Rethink Intune Deployment:
In some scenarios, deploying Field Service Mobile outside of the Microsoft Intune framework has resulted in noticeably faster app response times.
Performance challenges in Field Service Mobile are rarely caused by a single factor. In my experience, it’s the combination of small, intentional optimisations that delivers the best results for technicians in the field.
Would be keen to hear what has worked for others in real-world deployments.