Dynamics 365 Field Service : Configure geocoding for a custom table

Dynamics 365 Field Service enables businesses to deliver onsite service to customer locations efficiently. One of the core features that powers Field Service logistics is geocoding—the ability to convert an address into geographical coordinates (latitude and longitude).

This is vital for features like:

•  Work order location mapping
•  Route optimization
•  Resource scheduling
•  Proximity-based filtering

But what if your business has a custom table—like `Warehouse`, `Customer Site`, or `Supplier Location`—and you want to enable geocoding on that table too?

Let’s walk through how to configure geocoding for a custom table in a way that blends naturally with Field Service’s native capabilities.

What is Geocoding in Field Service?

Geocoding is the process of translating a physical address (like “123 Main Street, Delhi”) into coordinates (like `28.6139° N, 77.2090° E`).

By default, Field Service geocodes locations for:

•  Accounts
•  Work Orders
•  Bookable Resource Addresses

But with a few simple steps, you can extend this to any custom table that has address fields.

Prerequisites

Before we begin, make sure you have:

•  Dynamics 365 Field Service installed and licensed
•  Admin or System Customizer role
•  Access to Power Platform Admin Center
•  Custom table created with address fields (Street, City, State, Postal Code, Country)

Let’s assume our custom table is called `Warehouse`.

Step-by-Step Guide to Enable Geocoding for Custom Table

Step 1: Add Address Fields to the Custom Table

Ensure your custom table (e.g., `Warehouse`) has the following address fields:

| Logical Name                       | Display Name    |

| `address1_line1`                    | Street 1              

| `address1_city`                      | City                      

| `address1_stateorprovince`    | State/Province  |

| `address1_postalcode`            | ZIP/Postal Code |

| `address1_country`                 | Country         |

These fields are required by the geocoding process to compute coordinates accurately.

 Tip: These are standard address schema names. Using them allows Field Service features to detect and use them automatically.

Step 2: Enable Bing Maps Integration (Optional but Recommended)

Go to Advanced Settings → Administration → System Settings → General tab:

•  Find the Set Bing Maps Integration option and ensure it is enabled.
•  Enter your Bing Maps Key if it's not already present (usually added by your admin).

Step 3: Enable Geocoding for the Custom Table

1. Go to Power Apps Maker Portal

• URL: https://make.powerapps.com

2. Navigate to Your Solution → Custom Table (e.g., Warehouse)

3. Under the Data experiences section:

•  Enable Geospatial features
•  Choose Geocode addresses using Bing Maps

4. Click Save and Publish All Customizations

Step 4: Add Latitude and Longitude Fields

To store geocoded values:

 Create two custom fields:

•    `Latitude` (Decimal Number, Precision: 6)
•    `Longitude` (Decimal Number, Precision: 6)

Note: You can name them anything, but using `latitude` and `longitude` ensures compatibility with map controls.

Step 5: Configure and Use Power Automate for Geocoding (Optional for Advanced Use)

If you want to trigger geocoding automatically on record creation or update:

1. Create a Power Automate flow that calls Bing Maps API.

2. Update the record with the retrieved `Latitude` and `Longitude`.

3. Use this data for map visualizations or scheduling logic.

Alternatively, use Field Service’s built-in geocoding plugin, which will auto-trigger if the schema is correct.

Visualizing on the Map

Once geocoding is enabled and records have valid coordinates:

•  Use Map Controls on the table’s view or form.
•  Enable map view in Model-Driven App settings.
•  Use Proximity Search for filtering records by distance.

Conclusion

Enabling geocoding for a custom table in Dynamics 365 Field Service unlocks advanced routing, mapping, and scheduling capabilities. Whether it’s tracking warehouses, service centers, or remote assets—geospatial intelligence adds value across the board.

By following the steps above, you can integrate location intelligence into your custom tables seamlessly.