web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Answered

Lat/Long on Functional Location table not changing after address update

(3) ShareShare
ReportReport
Posted on by 85
When I create a new Functional Location, the Latitude and Longitude are auto-populated to the record.

If I ever have to update/fix the address on a Functional Location, these values do not update. Some administrators will change the addresses and I cannot count on them to manually update the lat/long.

Auto Geocoding is turned on. I assume this is an OOTB functionality since I cannot find any evidence of a flow/workflow running when the functional location is created.
 
What am I missing?
I have the same question (0)
  • Suggested answer
    Fameeda Yaseen Profile Picture
    449 on at
    When you create a Functional Location and set an address → Dynamics calls Bing Maps API (behind the scenes) → auto-populates Latitude & Longitude.
    When you update the address after creation → it does not trigger the geocoding logic again.

    In Dynamics Field Service, auto geocoding only runs on record creation by default. Microsoft did this likely to avoid excessive geocoding API calls, especially with large datasets.
    What You’re Missing / How to Fix It
    You need to manually re-trigger the geocoding logic when the address is updated. Here’s how you can fix it. Might be you can use the power automate job to trigger on update.
  • Verified answer
    Tom_Gioielli Profile Picture
    2,792 Super User 2025 Season 2 on at
    I don't think there is a simple way to retrigger the OOB API call. You can resolve this by creating a Power Automate flow and using the Bing Maps connector to get your latitude and longitude details using the new address information.
     
  • Anne Stanton, MCSE, MBA, CRM rMVP #7 Profile Picture
    65 on at
    This is by design as the call is only running on create. If you need Lat/Long updated onchange or onsave (onsave might generate a lot of unnecessary calls) then more has to be added.
     
    Ideally on change of perhaps Street 1 and/or zip code the lat/long fields would be set to null and a new call to the API would be initiated to reset the fields.
     
    Anne 
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 45 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 27 Most Valuable Professional

#3
Soundari Profile Picture

Soundari 15

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans