Skip to main content
Gainsight Inc.

Action Type: Load to Company Person

Gainsight Standard Edition
This article supports Gainsight Standard Edition. This Edition is built on Gainsight's state of the art Matrix Data Architecture (MDA) platform, and is designed for customer success professionals for driving revenue, increasing retention, and scaling operations. To learn more about Gainsight Standard Edition, click here.

If you are using Gainsight Salesforce Edition, which is built on Salesforce and customer business data is stored in SFDC, you can find supporting documentation here.

 

Overview

Gainsight Person is an object model that has unique records to represent people in the real world. This object model has three objects as listed below:

  1. Person: The personal attributes of a person like his Name, Email, Mobile phone, Twitter profile, LinkedIn profile, etc. are stored in this object.

  2. Company Person: The attributes of a person in association with a company are stored in this object like Company name, Title/Designation, Office phone, Manager, etc.

  3. Relationship Person: The attributes of a person in association with a Relationship at a specific company (a project implementation or business unit) are stored in this object.

To learn more on the Gainsight Person Model, refer Gainsight Person Object Model.

This article guides you to create a rule that loads data from external entities to the Person and Company Person objects.

Prerequisites

  • Ensure that records in the Company object are available to which you apply lookup for person records from the Company Person object.

  • Ensure that required fields are available in the dataset that are required to match with fields in the lookup object in the Import Lookup Configuration. For more information, refer the section Setup Action: Load to Company Person.

Create a Rule

  1. Navigate to Administration > Rules Engine.

  2. Click +Rule to create a new rule. Create Rule page appears.

  3. Enter the following details:

  • Rule For: Select Company
  • Rule Name: Assign a unique rule name
  • Description (Optional): Description to this rule
  1. Click Next.

Rule Setup.gif

Setup Rule

If you store your business contacts data in a csv file and upload into any S3 bucket, you can create a dataset by fetching data in this csv file. For the detailed instructions on how to create a dataset from a csv file in the S3 bucket, refer S3 Dataset Task in Rules.

Setup Action: Load to Company Person

Once the S3 dataset is created, execute the following steps to load data into Person Object.

  1. Navigate to Setup Action page.

  2. Click + ACTION.

  3. Select Load to Company Person as the Action.

  4. (Optional) Enter a description in the Description field.

Setup Rule Action.gif

  1. Select Upsert as the Operation. This helps to update the existing records in the Company Person and create new records.
  2. Derived field mappings:

a. Click the Import Lookup icon in the actions column for Company ID target field. The Data import lookup configuration window appears.

b. In Data import lookup configuration window, configure as shown below:

i. Lookup in (object): Select Company

ii. Click + in the Match By field.

iii. For field matching between source and lookup objects, select Company Name and Name, in the Source dataset and lookup object (Company) respectively.

Company Name field represents the name of a company and it is a field to store company data in the S3 dataset. When values in the Company Name field in the source S3 dataset and Name field in the lookup object (Company) match, it populates GSID from the Company object to Company ID field in the Company Person object. You can even use multiple fields for matching to identify a specific record in the lookup object.

Note: Field name Company Name is used in the S3 dataset just for reference only, you can create a field with different name.

iv. Click Apply.

Setup data import lookup.gif

For more information on data import lookup, refer Data import Lookup.

c. Click the Import Lookup icon in the actions column for Person ID target field. The Data import lookup configuration window appears.

d. In Data import lookup configuration window, configure as shown below:

i. Lookup in (object): Select Person.

ii. Click + in the Match By field.

iii. For field matching between source and lookup objects, Select Email in the Source dataset and lookup object (Person) respectively.

Email is a field in both the source S3 dataset and lookup object (Person). If the values in both these fields match, it populates GSID from Person object to Person ID field in the Company Person. You can even use multiple fields for matching to identify a specific record in the lookup object.

If there are records in the Person object that match the configuration above, new record in the Person object is created and GSID of new record is populated in the Person ID field in the Company Person object.

iv. Click Apply.

Data Mapping.gif

e. Click +DERIVED MAPPING FOR COMPANY PERSON: Click this to add more derived mappings for loading data into the GSID data type fields in the Company Person object.

f. + DERIVED MAPPING FOR PERSON: Click this to add more derived mappings for loading data into the GSID data type fields in the Person object.

  1. Field Mappings:

a. Map the Email field in the dataset with Person:: Email (EMAIL) field. This is a mandatory field mapping. When you select target field as Person::Email, this target field is included in identifiers automatically and you cannot able to remove the selection.

b. Map the remaining fields from the dataset and the target object. If required, select the Include in Identifiers checkbox to any of the target fields while mapping.

c. + FIELD MAPPING: Click this button to add additional custom field mappings.

  1. + CRITERIA: Click this button to add additional criteria to fine tune which data is synced, or to perform different or multiple actions based on the same data points.
  2. Click SAVE.

Field mappings.gif

  1. Click RUN NOW, to execute the rule now.You can also <<schedule the rule>>(TBA) to run later.

 

 

  • Was this article helpful?