Geocodes play a crucial role in location-based services in Salesforce Field Service. The Latitude and Longitude fields on a Service Appointment record are populated by Data Integration Rules using the Data.com geocoding service. When geocodes are missing on Service Appointment records, the cause is typically one of the following:
This article provides a step-by-step guide to diagnose and resolve missing geocodes on the Salesforce Field Service Service Appointment object.
The following steps cover how to troubleshoot missing geocodes on Service Appointments, starting with determining whether the problem affects all records or only some.
Begin by determining whether the geocode issue is consistent across all Service Appointment records or if it is intermittent.
a) Issue Across All Records:
If the problem persists for all Service Appointment records, the Data Integration Rule for geocoding is likely inactive. Follow these steps to verify:
b) Intermittent Issue:
If the issue is sporadic and not affecting all records, proceed with the following steps:
Note: Ignore the FSL__InternalSLRGeolocation__c field. This field is used for internal Salesforce Field Service scheduling calculations and is not related to Data.com geocodes.
If the geocode issue is intermittent, follow these steps to check the status of the geocoding process on a specific record:
Review the status. If the status shows something other than "In Sync" (for example, "Skipped"), this indicates that custom triggers, flows, process builders, validation rules, or the Data.com service encountered an error during the geocoding transaction.
To identify the root cause of intermittent geocoding failures, follow these steps:
A CSV file containing error details downloads automatically. Analyze the errors and look for issues related to custom processes, triggers, or the Data.com geocoding service.
Troubleshooting missing geocodes on the Salesforce Field Service Service Appointment object requires verifying that Data Integration Rules are active, checking geocode status on individual records, and reviewing Data Integration Metrics for errors caused by custom processes or the Data.com service. Resolving these issues restores accurate geocode population and ensures the efficiency of location-based services in your field service management system.
000692560

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.