We have had Resource User latitude and longitude data overwritten in D365 Field Service twice now as the address held in the Active Directory is not the actual home address of a technician but an office address.

The actual latitude and longitude data had been loaded into D365 but it was overwritten by the geocoded data from the user AD address. Active Directory does not contain latitude and longitude data, only an address.

We would see advantage is being able to disable the auto geociding in the user record to prevent these data overwrites. Or as an alternative to include latitude and longitude data in the Resource record and use that instead which would be more versatile as it would allow better scheduling of non user resources.
Needs Votes