Dynamics 365 Field Service : Customize the mobile app including forms, views, pages, and navigation

Field technicians rely heavily on mobile applications to execute tasks efficiently while on the go. Microsoft’s Dynamics 365 Field Service mobile app, built on Power Apps, provides a powerful and flexible platform for field operations. But its real power comes when it’s tailored to match your organization’s exact field processes.

In this blog, we’ll explore how to customize the Field Service mobile app, including forms, views, pages, and navigation, to streamline user experience and boost productivity for your field workforce.

Understanding the Dynamics 365 Field Service Mobile App

Before diving into customization, it’s important to note:

• The Field Service mobile app is a Model-Driven App, powered by Power Platform.
• Customizations are made within Power Apps Studio or the classic app designer, depending on the component.
• Changes reflect across mobile and web apps, but you can control visibility based on the form factor.

Customizing Forms for Mobile Technicians

What are Forms?

Forms define how data is displayed and captured for specific tables (entities), such as Work Orders, Bookable Resources, or Assets.

How to Customize Forms

•  Navigate to Power Apps > Solutions > Entity (e.g., Work Order) > Forms.
•  Choose the form you want to edit (e.g., Work Order - Mobile).
•  Use sections, tabs, and controls to design the layout.
•  Add only relevant fields for mobile users — keep it concise and optimized for touch.

Best Practices

•  Use business rules or JavaScript to show/hide fields based on conditions.
•  Consider using custom controls (like pen input, toggle switches) to enhance usability.
•  Hide irrelevant fields from mobile using the "Show on Mobile" setting.

Customizing Views

What are Views?

Views define how records are listed — for example, a list of open Work Orders or upcoming bookings.

How to Customize Views

•  Go to Power Apps > Tables > Views.
•  Select or create views like:
•    My Work Orders
•    Open Bookings
•  Define columns, sorting, filters, and layout.

Mobile Optimization Tips

•  Show only key fields: e.g., Work Order Number, Status, Location.
•  Ensure the primary field is clear (this shows in the mobile list view).
•  Use editable grids if inline updates are needed.

Customizing Pages (App Pages)

What are App Pages?

App Pages provide dashboard-like or multi-tab landing pages. These are great for giving mobile users an overview or quick access to key info.

How to Create App Pages

•  Open the modern app designer (Power Apps > Apps > Edit your Field Service app).
•  Choose + New Page > App Page.
•  Add components like views, charts, or forms.

Example Use Cases

•  A Home Page that shows Today’s Bookings, Pending Work Orders, and KPIs.
•  A Job Summary Page combining customer info, work order details, and service tasks.

Customizing Navigation

What is Navigation?

Navigation controls the menu items that technicians see when they open the mobile app.

 How to Customize It

 Open Power Apps > Apps > Edit Field Service App.

 In the site map editor, define:

•    Areas (e.g., Field Service)
•    Groups (e.g., Work Management)
•    Subareas (e.g., Work Orders, Bookings, Customers)

Mobile-Specific Considerations

•  Keep it simple — only include essential entities.
•  Order items by usage frequency.
•  Use icons to make the navigation visually intuitive.

Syncing & Testing

Once you’ve made customizations:

1. Save and publish changes.

2. Use the “Mobile Preview” in Power Apps for basic testing.

3. Test in the Field Service Mobile App on real devices to verify performance and usability.

4. Ask users for feedback and iterate!

Final Thoughts

A well-customized mobile experience makes a huge difference for field users. By optimizing forms, views, pages, and navigation, you ensure that technicians spend less time on screens and more time delivering value to customers.

The key is user-centric design: only show what’s necessary, make navigation intuitive, and tailor the experience to field workflows.