Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Dynamics 365 Field Service mobile app is built on a model-driven app. General guidelines and best practices for performant apps and performance consideration for model-driven apps apply too.
Remove Console.log from production code
Logging data to the console increases memory pressure because the console prevents items from being cleaned up. Avoid logging data to the console during production to prevent unintentionally exposing sensitive data to the end user. This includes console.log, console.warn, and console.error.
If not using QuickNotes, remove QuickNotes WebResource
The QuickNotes control bundle exists twice within Field Service: once as a PCF control and once as a web resource. If QuickNotes control (or any other control) isn't used, remove the control's bundle.js file from the web resources in the form properties. This prevents downloading the control code when not necessary.
The bundle can be removed by going to the booking and work order form for the bookable resource booking entity, opening Form Properties, and removing the cc_MscrmControls.FieldControls.QuickNotesControl/bundle.js item from the Events tab.
Minify Office UI imports in PCF controls
If using the @fluentui/react library for interactive UI components, it's possible to import more modules than intended based on how the import is defined. By being specific about the path that you are importing components from, you can dramatically reduce the size of your components (resulting in less data needing to be downloaded).
For example:
import { Button } from '@fluentui/react'
should be written as:
import { Button } from '@fluentui/react/lib/Button';
Use connected forms to minimize navigation across different entities
Field Service lets you use data from different tables on a form. Fewer navigation actions means less loading time. Form components have a lower peak memory value when navigated to, in comparison to scenarios that use quick-find navigation instead.
For more information, see Edit the booking and work order form.
Remove unused controls from the app
If app users don't use certain controls in the mobile app, remove them to reduce memory usage. Having unnecessary controls in the form increases the memory consumption of the app, leading to performance degradation. For example, the timeline control is included by default on several tables and forms. If your scenario doesn't use the timeline, remove it to reduce memory consumption.