The Maps Connector for ArcGIS pushes Salesforce record data to ArcGIS Server, so field data entered or updated in Salesforce automatically syncs to ArcGIS Server. For example, if your Salesforce org has a custom object for a Fire Hydrant and a user updates a Fire Hydrant record, Salesforce Maps can push that update to ArcGIS Server.
Before you begin, you should already have a custom object in your Salesforce org that you want to sync.
This article explains how to configure a one-way sync between Salesforce and ArcGIS Server using the Maps Connector for ArcGIS. It covers setting up the required fields on your object, importing existing ArcGIS data, mapping fields with Click2Create, configuring the ArcGIS object in Salesforce Maps, and scheduling the sync batch.
Setting up an object requires you to add a few fields to the object. These fields tell Salesforce Maps how, and where, to sync the field data. You need to add the following fields to your object. You do not need to enter any information into these fields yet, you just need to create them.
ISNULL ( FID__c ) || LastModifiedDate > Sync_LastPushed__c + 0.000011*10
This formula checks two conditions: whether the FID field is blank, which means Salesforce Maps needs to create a new record in ArcGIS Server, and whether the record has been modified since it was last pushed, which means Salesforce Maps needs to update the existing record in ArcGIS Server. The API name for the Last Pushed field may be slightly different in your org.
Note: If you are working with more than 1,000 records in your sync, we recommend adding additional logic to the formula field to limit the number of records included in each batch. Adding an ISCHANGED operator tied to a particular field can help reduce the batch size. The ISNULL(FID__c) check is required, but you can customize the remaining logic for your use case. When the checkbox is checked, Salesforce Maps knows the record needs to be synced.
For more information on creating fields in Salesforce, see Create Custom Fields.
Before the sync goes live, you need to perform an initial import from ArcGIS Server. This establishes a starting point where both Salesforce and ArcGIS Server data are known to be in sync. Manually export your ArcGIS data in a format Salesforce accepts, such as CSV, then import it into Salesforce using the Data Loader or the Data Import Wizard.
While doing this import, set the Last Pushed time to about 30 minutes in the future. For example, if you are importing your Fire Hydrants at 11:00 AM, set the Last Pushed time to 11:30 AM. You can then begin using the sync after 11:30 AM.
Next, define which fields in Salesforce map to fields in ArcGIS. To do this, create a field set and a Click2Create template, described in Maps Connector for ArcGIS Enhanced Click2Create.
The field mapping in the Click2Create template determines which fields sync to ArcGIS Server. For example, if your Salesforce records have a Description section, map that section to the corresponding Description field in ArcGIS Server. Salesforce fields on the left are pushed to the ArcGIS Server fields on the right, and not all fields need to be mapped.
Keep this layer name handy, since you will need it when configuring an ArcGIS object in the next section. Click2Create still works as it did prior to the Spring 18 release, so you can still create Salesforce records based on ArcGIS data, such as creating a Case record on a Street Light Feature.
Now you can configure your ArcGIS objects in Salesforce Maps. ArcGIS objects are those that have a corresponding Feature in ArcGIS Server. If you do not want to sync a particular object to Server, simply do not create an ArcGIS object for it.
Setting Name: Give the setting a helpful name. For example, if you are pushing Tree records to ArcGIS Server, you might call this your Tree Sync setting.
Object: The Salesforce object you want to sync to Server.
Feature ID: Maps to the FID field you created earlier.
Last Pushed: Maps to the Last Pushed field you created earlier.
Updated: Maps to the IsUpdated field you created earlier.
Layer: Select the Salesforce Maps layer that has the Click2Create template.
Template: Select the Click2Create template on the Maps record.
Feature Layer URL: Copy and paste your Feature Layer URL into this field.
Authentication Token: Generate a token in the modal, either by pasting a token or generating one based on the Feature Layer URL. Generating a token requires valid user credentials. Salesforce Maps only supports short-term ArcGIS tokens.
Select Save. Your ArcGIS object can now be synced.
For more information on configuring Click2Create, see Click2Create Configuration.
Once you have an ArcGIS object configured, you can use Click2Create to create new Features in ArcGIS Server directly from Salesforce Maps. For example, suppose you want to create a Tree record and have it appear in ArcGIS Server.
At this point, the new tree you created is automatically pushed to ArcGIS Server after you schedule a batch.
Syncing to ArcGIS Server requires a batch job. The batch job collects new or updated records and sends them to ArcGIS Server. This batch job is limited to processing up to 1,000 records; exceeding that limit causes a "Too many SOQL queries: 101" error and the job fails to execute.
Note: Make sure the records collected for a batch (records where the IsUpdated field is set to true) have latitude and longitude populated, otherwise the batch will fail to run.
Run this batch: You can run a batch once or multiple times, for example if you want a one-time push of a large number of records.
Batch Name: For a recurring batch, provide a name so you can remember what you are syncing.
ArcGIS Object: The ArcGIS object you configured in the previous step. This example uses the Tree Sync object.
Repeats: Designates the frequency of the sync.
When you are ready, select Schedule Batch.
000391886

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.