FSM Stored Coordinate Maintenance
Field Service Management (FSM) maintains cached address lookups and can combine stored coordinates into a Geolocation value. For the relationship with map display and tracking, see FSM Maps and Location Tracking.
The Field Service Scheduled : Geo deployment, customdeploy_nx_geo, assesses cached address-geocoding results before selecting coordinate migration work. Migration is selected only when the preceding maintenance checks produce no actions.
Old cached lookups can expire when legacy compliance maintenance is disabled. Migration is assessed only after earlier checks produce no actions. It fills missing Geolocation from nonzero stored coordinates. The following diagram compares cached lookup expiration with coordinate migration:
When legacy coordinate-compliance maintenance is not enabled, old cached address-geocoding results are marked for expiration. Expiring a cached lookup result does not itself clear latitude, longitude, or Geolocation already stored on a business record.
The migration assessment selects task and project task records that have Field Service Latitude and Field Service Longitude but no Field Service Geolocation value. It also includes field service asset records with their corresponding latitude, longitude, and Geolocation fields.
For selected records with nonzero latitude and longitude, migration populates Geolocation from the existing coordinates. The resulting field value confirms that record update. Selection for migration does not establish that processing is currently running.
The address lookup described in Task Coordinate Calculation from an Address calculates task and project task coordinates from Field Service Address. Scheduled migration instead combines already stored latitude and longitude into Geolocation. It does not request new coordinates from an address.
Verify migration by checking both the affected record's Geolocation value and the execution result.