Edit the mobile application

An HVAC technician opens the mobile app to prepare for an annual inspection. They need the booking time, the customer location, the equipment being serviced, and the inspection tasks. Your customization decisions determine how easily they find that information and record the results.

Because Field Service Mobile is a model-driven app, you customize it with Power Apps. Start with the technician's task, then decide whether the change belongs in navigation, a view, or a form.

Choose the right component

Three components shape how technicians work with information:

• Navigation: Determines which pages technicians can open and how those pages are grouped. The underlying navigation structure is also called the site map.
• Views: Determine how lists of records appear, including columns, sorting, and filters. A view helps a technician find a record.
• Forms: Determine how information about an individual record appears. A form helps a technician review or update that record.

For example, adding a customer assets page makes that table easier to reach. Including the serial number in an asset view helps technicians distinguish similar pieces of equipment. Placing relevant work order fields together on a form helps them review a job without moving between unrelated sections.

Use an account with permission to customize model-driven apps, such as a system administrator or system customizer. Make and test changes in a development or test environment before deploying them through your organization's solution management process.

Edit navigation and views

Sign in to Power Apps, select the environment with Field Service installed, and locate Field Service Mobile under Apps. Open the app for editing in the app designer.

You can also open the designer from the Dynamics 365 app selector: select the ellipsis (...) on the Field Service Mobile app and select Open in App Designer.

Organize pages around technician work

The current app designer presents navigation as groups and pages in the Pages pane. You don't need to use the classic site map designer.

To add a table page:

1. Select Add page on the command bar.
2. Select Dataverse table and choose the table that technicians need, such as Customer Asset.
3. Complete the page selection and select Add.
4. Organize the page in an appropriate navigation group. Add or rename groups when that makes the purpose clearer to technicians.

Review the existing pages before adding another entry for a table. To remove an unnecessary group or page, select its ellipsis (...) in the Pages pane and select Remove from navigation.

For more information, see App navigation in model-driven apps.

Make record lists useful on a phone

A navigation entry is only useful if technicians can identify the record they need. For the HVAC example, a customer asset view might display the asset name, product, and serial number, with active assets listed in name order.

To configure a public view:

1. In Power Apps, open the solution that contains the table you want to customize.
2. Open the table and select Views.
3. Open the relevant public view in the view designer.
4. Adjust the columns, their order, sorting, and filters to support the technician's task.
5. Save and publish the view, and make it available for the table in the mobile app designer.

Keep the most useful identifiers near the start of the view. A wide desktop list can require unnecessary scrolling on a phone. View filters help focus the list; they don't replace record-level security.

For more information, see Understand model-driven app views and Edit the navigation and views on the mobile app.

Edit the combined booking and work order form

A booking describes a scheduled visit, including the assigned resource and booking times. The work order describes the service job, including its tasks, products, and services. Technicians need both kinds of information, so the mobile app combines them on the Booking and Work Order form.

The form uses a form component control to display work order information inside the booking form. Editing only the booking table doesn't change every section of this combined experience.

Use the following mapping to choose the correct form:

For example, if technicians need a work order field alongside customer details, edit Work Order - Customer. If they need a change to the booking information, edit Booking and Work Order instead.

To edit a form:

1. In Power Apps, open your customization solution and the table identified in the mapping.
2. Select Forms, select the required form, and select Edit.
3. Use the form designer to add the required columns or adjust their placement and properties. A column must exist on the relevant table before you can add it to that table's form.
4. Select Save and Publish for each form you change.

Keep related fields together and retain the information technicians need to complete their work. Avoid removing fields or controls just because they aren't relevant to a single example.

For more information, see Edit the booking and work order form and Create, edit, or configure forms using the form designer.

Publish and check the technician experience

Publish the app changes as well as the forms and views you edit. Then test on a mobile device with a technician account, not only an administrator account. Check that:

• The intended pages appear in navigation without unnecessary duplicates.
• Views show the columns and records that the technician needs.
• A booking opens the expected combined form, with changes in the correct booking or work order section.
• The technician can read and update the required information with their assigned security roles.
• The layout works on the device's screen without hiding essential information.

If technicians work offline, also confirm that the required tables and records are included in the offline profile and test after synchronization. Adding a table to navigation doesn't automatically make its data available offline. The next unit explains how to configure that data.