Skip to main content
Gainsight Inc.

Configure Out of the Box Jobs

IMPORTANT
Gainsight is upgrading Gainsight Connect to the new Salesforce Connector. This article is applicable only to those Gainsight users whose Orgs have been upgraded from Gainsight Connect to the Salesforce Connector. To learn about the Gainsight Connect Upgrade, click here.

 

This article is the fifth in a series of Salesforce connector articles. Gainsight recommends you refer to the initial articles and then proceed with this article.

This article explains the default settings configured in Out of the box sync jobs. If you are not aware of different stages in a Data sync job, refer to the Create Data sync jobs article and then proceed with this article.

Overview

When you authorize a connection, Gainsight creates six out of the box data sync jobs. You can modify the jobs, if required. These jobs are used to sync the basic data required to perform routine operations in Gainsight. The six out of the box jobs are:

1..png

Picklist Sync Job

This job is named as Picklist Sync_ Connection name. (here Picklist Sync_Connect to SFDC). This job syncs data from Salesforce Picklist to Gainsight Dropdown lists. By default, this job does not have any dependencies. You can add a dependent job, if required. The Notification Details fields of this job contain the email address of the logged in user. You can add, edit, or delete email recipients. 

There are no configurations or mappings for this section. You can only schedule the execution of this job.

2..GIF

User Sync Job

This job is named as User Sync_ Connection name. (here User Sync_Connect to SFDC). This job syncs user data from the Salesforce User object to the Gainsight User object. By default, this job has a dependency on Picklist Sync job. You can add a dependent job, if required. The Notification Details fields of this job contain the email address of the logged in user. You can add, edit, or delete email recipients. 

  • In the job configuration stage, Source object is mapped to Salesforce User Object and target Object is mapped to Gainsight User Object. You cannot modify this setting. 
  • By default, there are five field mappings configured in this job. You can add, edit, or delete these field mappings. The mappings are: 
    • First Name -> First name 
    • Last Name -> Last Name
    • Email -> Email
    • Time Zone -> Timezone
    • Username -> Username

By default, the mapping between Username field from Salesforce and Username field from Gainsight is set as the Upsert key. You can select some other mapping as the Upsert key or even have multiple mappings as Upsert keys, if required. It is mandatory to configure at least one mapping as Upsert key.

  • There are no derived mappings configured for this job. You can add any number of derived mappings to populate values into the GSID type fields as required. For more information, refer the Data Import Lookup article.
  • The Filters section has two filters by default. These filters are configured to fetch only Standard and Active users. You can add, edit, or delete the filters as required. 
  • The Schedule section is not configured for this job. You can either schedule an execution or import data now with the available options. 

3..GIF

Company Sync Job

This job is named as Company Sync_ Connection name. (here Company Sync_Connect to SFDC). This job imports data from the Salesforce Account object and inserts it into the Gainsight Company object. By default, this job has a dependency on the User Sync job. You can modify the dependent job, if required. The Notification Details fields of this job contains the email address of the logged in user. You can add, edit, or delete email recipients. 

  • Since this job syncs data from Salesforce Account object to Gainsight Company object, the Source object is mapped to Salesforce Account object and target object is mapped to Gainsight Company object. You cannot modify this setting. 
    Note: To learn more about various objects available in Gainsight, refer to the Gainsight Data Management article.
  • By default, there are three field mappings configured in this job. You can add or edit the mappings.The mappings are:
    • Account ID  -> SFDC Account Id
    • Account Name -> Name 
    • Employees -> Employees

By default, the mapping between Account ID field from Salesforce Object and SFDC Account Id field from Company object is set as the Upsert key. You can select some other mapping as the Upsert key or even have multiple mappings as Upsert keys, if required. It is mandatory to configure at least one mapping as Upsert key.

  • By default, there are no Derived mappings, Filters, or Schedule configured for this job. However, you can configure these sections, as required.

4..GIF

Company Person Sync Job

This job is named as Company Person Sync_ Connection name. (here Company Person Sync_Connect to SFDC). This job imports data from the Salesforce Contact object and inserts it into the Gainsight Person and Company Person objects. This job is not present in Gainsight connect. By default, this job has a dependency on the Company Sync job. You can modify the dependent job, if required.The Notification Details fields of this job contains the Email address of the logged in user. You can add, edit, or delete email recipients. 

  • Since this job fetches data from Salesforce Contact object to Gainsight Person and Company Person Object, the Source object is mapped to Salesforce Contact Object and target Object is mapped to Gainsight Company Person Object. You cannot modify this setting. 
  • By default, there are five field mappings configured in this job. You can add or edit the mappings. The mappings are:
    • First Name -> First Name (Person)
    • Last Name -> Last Name (Person)
    • Email -> Email (Person)
    • Contact ID -> External Contact ID (Company Person)
    • Account ID -> External Account ID (Company Person)

The mapping between Email field in Salesforce Contact Object and Email field in Person object, is configured as the Upsert key. You can select another mapping as the Upsert key or even have multiple mappings as Upsert keys, if required. It is mandatory to configure at least one mapping as the Upsert key. 

  • By default, there are no Derived Mappings, Filters or Schedules configured for this job. You can configure them, as required.

5..GIF

Relationship Type Sync Job

This job is named as Relationship Type Sync_ Connection name. (here Relationship type Sync_Connect to SFDC). This job imports data from the Salesforce Relationship Type object and inserts it into the Gainsight Relationship Type object. By default, this job has a dependency on the Company Sync job. You can modify the dependent job, if required.The Notification Details fields of this job contains the Email address of the logged in user. You can add, edit, or delete email recipients.

  • Since this job fetches data from Salesforce Relationship Type object to Gainsight Relationship type Object, the Source object is mapped to Salesforce Relationship Type Object and target Object is mapped to Gainsight Relationship Type Object. You cannot modify this setting.
  • By default, there are two field mappings configured in this job. You can add or edit the mappings. The mappings are:
    • Name -> Name
    • Id -> SFDC Relationship Type Id (Person)

The mapping between Id field in Salesforce Relationship Type Object and SFDC Relationship Type Id field in Gainsight Relationship Type object, is configured as the Upsert key. You can select another mapping as the Upsert key or even have multiple mappings as Upsert keys, if required. It is mandatory to configure at least one mapping as the Upsert key.

  • By default, there are no Derived mappings, Filters, or Schedule configured for this job. However, you can configure these sections, as required.

6..GIF

Relationship Sync Job

This job is named as Relationship Sync_Connection name. (here Relationship Sync_Connect to SFDC). This job imports data from the Salesforce Relationship object and inserts it into the Gainsight Relationship object. By default, this job has a dependency on the Relationship type sync job. You can modify the dependent job, if required.The Notification Details fields of this job contains the Email address of the logged in user. You can add, edit, or delete email recipients.

  • Since this job fetches data from Salesforce Relationship object to Gainsight Relationship Object, the Source object is mapped to Salesforce Relationship Object and target Object is mapped to Gainsight Relationship Object. You cannot modify this setting.
  • By default, there are two field mappings configured in this job. You can add or edit the mappings. The mappings are:
    • Name -> Name
    • Id -> SFDC Relationship Id (Person)

The mapping between Id field in Salesforce Relationship Type Object and SFDC Relationship Id field in Gainsight Relationship Type object, is configured as the Upsert key. You can select another mapping as the Upsert key or even have multiple mappings as Upsert keys, if required. It is mandatory to configure at least one mapping as the Upsert key.

  • By default, there are no Derived mappings, Filters, or Schedule configured for this job. However, you can configure these sections, as required.

7..GIF

Data Sync Jobs for Renewal Center

If you are using Gainsight Renewal Center, two additional data sync jobs are created out of the box ; Opportunity Stage Sync and Opportunity sync jobs. 

Opportunity Stage Sync Job

This job syncs data between Salesforce Opportunity Stage object and GS Opportunity Stage object. This job has a dependency on the Company sync job. By default, this job has 11 field mappings. The mapping between Opportunity Stage Id field in Salesforce and External Id field in Gainsight is used as the Upsert key. Gainsight doesn’t recommend changing the Upsert key. The complete list of field mappings is  shown below:

new.png

This job does not have any derived mappings or filters, by default. However, you can add them, as required and schedule the execution or run the job instantly. 

Opportunity Sync Job

This job syncs data from the Salesforce Opportunity object to Gainsight’s GS Opportunity object. This job is dependent on the Opportunity Stage sync job. This job has 11 field mappings by default. Apart from the 11 field mappings, you must map another four mandatory fields. The fields to be mapped are given below (the names provided in the Salesforce Field Name column below are only for representation purpose. The names of the fields can vary in your Salesforce environment)::

Salesforce Field Name Gainsight Field Name
Forecast Amount Forecast amount
Target  Amount Target  Amount
Final Amount Final Amount
Target Date Due Date

Apart from these fields, you must also map custom fields (if any), to ensure that Opportunity data is successfully synced back to Salesforce when a user modifies an opportunity. By default, the mapping between Opportunity ID field in Salesforce and External Id field in Gainsight is used as the Upsert key. 

9..GIF

This data sync job has four Derived Mappings:

  1. The first derived mapping uses Direct Lookup (to User object) to populate GSID to the Created By field in GS Opportunity object. The matching is between the Created by ID field in Salesforce and SFDC User Id field in Gainsight User object.  

10..GIF

  1. The second derived mapping uses Direct Lookup (to User object) to populate GSID to the Modified By field in GS Opportunity object. The matching is between the last Modified By ID field in Salesforce and SFDC User Id field in Gainsight User object.  

11..png

  1. The third derived mapping uses Direct Lookup (to User object) to populate GSID to the OpportunityOwner field in GS Opportunity object. The matching is between the owner ID field in Salesforce and SFDC User Id field in Gainsight User object.

12..png

  1. The fourth mapping uses Direct Lookup (to Company object) to populate GSID to the Company field in GS Opportunity object. The matching is between the Account ID field in Salesforce and SFDC Account Id field in Gainsight Company object.

13..png

CAUTION

  • If you have configured a field in Salesforce Connector, you must not delete the field from Data management page. This breaks the Renewal Center deployment. 
  • You must not create any formula fields (calculated fields) in the GS Opportunity object. This prevents Renewal Center from synchronizing updates.

See Also

  • Was this article helpful?