Functional location of assets and work orders in Dynamics 365 Field Service

Field Service organizations often service customers that have large or complex worksites - like a warehouse or a multi-story office building. In such cases, it's important that a technician can find specifically where they need to go to perform their work.

Functional location in Field Service allows for more location granularity on a few relevant Field Service entities, such as:

  • Within a service account
  • On an asset
  • On a specific work order

Additionally, functional locations can be represented by hierarchical relationships. For example, a printer might be located on the third floor, in building A on a customer's campus. This relationship would be represented as the following nested relationship:

  • Building A
    • Floor 3
      • Printer 1

In this article, we'll look at how to define functional relationships within Field Service.


  • Field Service v8.8.x.

Create a service account (optional)

First, create a service account or choose an existing one if you wish to use functional locations in association with service accounts. This is optional because functional locations can be used without being associated to service accounts. A service account is required to create a work order and the address of a service account will be used as the work order's address if a functional location is not defined, or if the functional location does not have a work order.

Add an address to the service account if applicable and geocode the record. You can see that the service account record is geocoded if it appears on the map and the latitude and longitude fields have values.

Screenshot of an account entity with a map populated.


In Field Service settings, there is a setting called Auto Geo Code Addresses. Set this field to Yes to have records autogeocoded as addresses are entered.

Create functional locations

Next, we'll create a functional location on a service account.

From the service account, go to the Assets and Locations tab. Select New location.

Screenshot of the assets and locations tab on an account record.

Give the location a name and then save. The new location will appear in this list, and can be dragged around and even nested as necessary.

In our example, we've created "Building A Roof" as a location under "Building A," which is located on the Bellows College Campus. The following screenshot shows this relationship in the list of functional locations on the service account.

Screenshot of the assets and locations on a service account.

Select any location in the list for more details, such as latitude and longitude.

Screenshot of a functional location details form.

Create or add assets to the functional location tree

Often, technicians must perform their work on a customer asset, which exists at a specific location at a work site.

Assets can also be associated directly to a functional location, making it easy for technicians to find and perform their work.

From the service account's Assets and Locations section, select the Show Assets option to see a list of associated assets.

Screenshot of the show assets option on the functional location list of a service account.

To add a new asset, select the ellipses icon, and either add a new asset, or relate an existing asset to this particular location.

Screenshot of the option to add a new asset or add an existing asset.


You can't drag a sub asset to a functional location different from the parent asset's functional location. When dragging an asset under a new parent with a different functional location, the asset's functional location will be cleared, and the parent's functional location will be used instead.

Search the functional location tree

Use the search bar to search for functional locations and associated assets. When searching, check the Show Assets box to include assets in search. Matching search results are highlighted and bold.

The number of search matches are shown beneath the search bar.

Functional location tree in Field Service, showing the search bar and the collapse and expand all options.

For larger or more complex trees, you can also expand or collapse all the results by using the Plus and Minus icons at the top of the tree, as seen in the previous screenshot.

For a guided walkthrough, check out the following video.

Use functional location for work orders

Once defined, functional locations help flesh out work order details, once again making it easier for technicians to see where they must perform their work.

As seen in the following screenshot, functional locations can be associated directly to the work order.

Screenshot of the functional location field on a work order.

Add a functional location or add a customer asset within that functional location.

Once the functional location is selected, you'll see that more detailed information will appear in the Location tab of the work order. If the functional location has a specific address, this information will populate on the Locations tab. If the functional location has no address, but has a latitude and longitude, no address will populate, but the latitude and longitude will.

Add multiple functional locations to a single work order

Use more work order incidents to define more work that needs to be done in addition to the primary work order incident.

Screenshot of a work order incident.

For each work order incident, you can define a functional location in scenarios where they must be completed at a different location than the one defined on the work order.

For example, imagine as part of one work order, a technician needs to go to three different buildings to perform a different task at each. In this scenario, add three work order incidents with each one having the respective functional location. Use the primary incident duration as either the most important work order incident or the location that the technician should travel to first.

Screenshot of a work order with related incidents.


Work order address only reflects the functional location on the work order and on the primary incident type, not the location of the additional incident types.

Use functional locations on the mobile app

Technicians can see the functional location of a work order on the Dynamics 365 Field Service mobile app.

Device render with the Field Service mobile app, showing a booking and a location on a map.

Technicians can also view and interact with functional location and customer asset hierarchies on the mobile app.

Device renders with the Field Service mobile app, showing asset hierarchies and functional locations.


Internet connectivity is required to view and interact with functional location and customer asset hierarchy trees on the Field Service mobile app.

For a guided walkthrough of functional locations on the Field Service mobile app, check out the following video.

Use functional location for cases

In cases where organizations start with a Case in their workflow, functional locations can be associated there as well.

On a case record, go to the Field Service section, and associate a functional location there.

Screenshot of the Field Service tab on a case.

Use functional location for agreements

To use functional locations on an agreement, select an agreement. Go to Agreement Booking Setup, and then Agreement Booking Incident, where you can associate a functional location.

Screenshot of an agreement booking incident.

Configuration considerations

  • Multiple accounts can be associated to a functional location tree.
  • Field Service technicians can see functional locations from their Field Service mobile apps, but cannot see or manage the larger location and asset hierarchies.

Functional location is not automatically associated to account in custom apps

  1. Open any custom app designer where this issue is seen.
  2. Add functional location entity to the app from Add > Entities.
  3. Select form components of functional location entity, uncheck All and select only quick create form for functional location.
  4. Publish the app and verify that functional location form will open quick create form in the tree view control.
  5. Newly created functional locations should appear in tree view control.