Use functional locations
A service account can identify the customer site without telling a technician where to find a particular air-conditioning unit. A large campus can have several buildings, each with equipment on different floors or roofs.
Functional locations describe these places in more detail. They help the technician find the worksite and distinguish the location of equipment from the equipment's component structure.
Plan the location hierarchy
For the annual HVAC inspection, a location hierarchy might contain:
- Customer campus: The overall site.
- Building A: A location within the campus.
- Roof: A location within Building A.
Rooftop Unit 01 is the customer asset at the Roof functional location. Compressor 01 can be its child asset. The roof isn't a parent asset, and the compressor isn't a functional location.
Use a Parent Functional Location to place a location within another location. A room can belong to a floor, which belongs to a building. Choose enough detail to help technicians find work without creating unnecessary levels that the organization can't maintain.
A functional location doesn't replace the work order's service account. Locations can be created independently of accounts, and multiple accounts can be associated with a functional location hierarchy. Check the account and location together rather than assuming that a place name establishes which customer receives the service.
Location names also aren't a substitute for useful address information. For example, distinguish the roof of Building A from the roof of Building B, and maintain the service address appropriate to each worksite.
Create locations and associate equipment
To create a location from an account:
- In Field Service, change to Service. Under Customers, select Accounts and open the service account.
- Select Assets and Locations.
- Select the ellipsis (...), then select New location.
- Enter a Name and Service Address.
- Select a Parent Functional Location if the new location belongs within an existing hierarchy.
- Complete other information as needed, then select Save and Close.
The additional fields include Functional Location Type, Cost center, Open date, Email address, and Primary time zone. Use them where they support the organization's location-management needs.
For example, a functional location type can group locations such as buildings or rooms. Administrators create these types under Settings > Functional Location Types. Types can also support applying property templates consistently to locations of the same kind.
Create the campus, Building A, and Roof locations with the appropriate parent relationships. You can also drag a location into its place in an existing hierarchy. Review the saved structure to make sure that the Roof location belongs to the intended building.
Add assets to a location
On the account's Assets and Locations tab:
- Select Show assets.
- Select the target functional location, such as Roof.
- Select the ellipsis (...), then select Add existing asset.
- Search for and select Rooftop Unit 01, and save the association.
If the equipment doesn't have an asset record yet, use New asset instead. Enter its asset information and account, then save. Don't create a second record just because the existing asset doesn't yet appear at the location.
Field Service doesn't allow a subcomponent to occupy a different functional location from its parent asset. If you move a component under another parent at a different location, it takes the new parent's location. Review both relationships when equipment moves.
Use the tree's search box to find a location. Select Show assets to include equipment in the search, then expand the matching branch to verify the result. This is useful when several buildings contain similarly named rooms or units.
Identify the work location on work orders
Functional locations are supported on work orders. In the current work order form, open General, scroll to the Location section, and select the functional location for the work.
The work order's Functional Location represents the location of the primary incident. For the inspection of Rooftop Unit 01, check that the primary asset is the correct unit and the functional location is the roof of Building A. An asset selection doesn't remove the need to verify the work location.
If another incident on the same work order covers equipment in Building B, select the appropriate functional location on that incident. Incidents can refer to different locations even though the work order has one primary location.
Before releasing a work order, check:
- Service account: The account receiving service.
- Customer asset: The specific equipment associated with each incident.
- Functional location: The place where each incident's work occurs.
- Service address: The address the technician needs to reach the worksite.
If no functional location is selected, Field Service uses the work order's service address. If that address is also missing, it uses the address of the contact who reported the issue. Verify the resulting details rather than relying on an unintended fallback.
Agreement booking incidents can also reference functional locations. Include the location with the associated asset when defining recurring work so the generated service records have useful site context.
Find locations in the mobile app
Technicians can view a work order's functional location in the Dynamics 365 Field Service mobile app. With an internet connection, they can also view and interact with functional location and customer asset hierarchies.
In the mobile app's standard work order form, open the Location tab, open the functional location, and select Assets and locations to review the hierarchy. Check the equipment under the expected building and roof before starting the inspection.
Note
Filtering functional locations by service account isn't supported in the offline-enabled Field Service mobile app. Don't assume that an offline location lookup has the same filtering as the connected app or that the interactive hierarchy is available offline.
For more information, see Create functional locations.