Gainsight administrators can now create and manage the Matrix Data - Objects in the Data Management page.

As an analogy, a Matrix Data - Object and its field(s) can be thought of as a database table and its columns.      

Data Management can be accessed via Administration > Operations > Data Management.

This article describes how to:          

To access the object list page, navigate to Administration > Operation > Data Management.

Prerequisites

Contact Gainsight Customer Support (support@gainsight.com) to enable Redshift if object lookup functionality is required.

Limitations

  • All of the objects, including out-of-the-box objects, (read-only objects) and custom objects are displayed.
  • MDA object fields have a maximum limit of 250 characters.

Permissions

In order to access the Data Management console, and be able to view and load data, a user must have access to the visual force Page JBCXM.COM.

Creating Matrix Data - Object manually

To create an MDA object:

  1. Navigate to Administration > Operations > Data Management. Click +Object.
  2. In the Create Object dialog, enter the following details:
  • Object display name: The easily understandable object display name that you want to create.
  • Object name: System defined object name with a suffix of __gc.
  • Object description: A description of the object being created.
  1. Select Manual and then click NEXT. Add Field screen appears.

Adding Custom Fields in an Object

  1. Enter the following details in the Add Field screen:
  • Display Name: The easily understandable display name.
  • Field Name: The system defined field name with a suffix of __gc.
  • Data type: The data type of the field being created.
  • Currency Code: You can see this field when you select data type as Currency only. Select a currency code from the list. For the list of currency codes supported, refer Supported Data Types.
  • Default Value: The default value that you would like to insert in the object field.
  • Decimal Places: You can see this field when you select data type as Currency, Number, or Percentage only. Assign the number of decimal places on the values in the field. By default, assigned decimal places is 0. 

Decimal_Places.png

  • Mapping: Select either SFDC or Gainsight mapping. Depending on the selection here, either SFDC Mapping or GS Mapping list box appears.
  • SFDC Mapping/GS Mapping: Map the field being created with an SFDC object or Gainsight object, if any.
  • Category: You can see this field when you select data type as Dropdown list or Multi select dropdown list. Select a category from the dropdown list.  
  • Controller: This field appears only when you create a Dependency field and assuming Controller field has already been created. Select a Controller field here. Controller and Dependent fields are tied to a different category which has a list of dropdown items. Each item in the controller category can control a set of items in Dependent category. 

    You can see the Controller field here only when a Dependency is created between the Controller and Dependent categories. To learn more about this, refer Dropdown list and Multi select Dropdown list.

Controller Category.png

  • Description: The description of the object being created.
  • Hide in reporting: If you select this, the field will be hidden in the Reporting functionality.
  • Required: By setting this constraint, the field is not allowed to ingest a null value record while importing data.
  • Enable lookup: This allows the object to lookup to another object while ingesting data into this object. When you select this checkbox, the following three fields are displayed:
    • Object: Select the source object from which data will be ingested into this field.
    • Field: Once you select an object, its corresponding fields are displayed here. select the source field to which lookup is enabled from the current field.
    • On Delete: This field allows you to reset records in this field, when the corresponding lookup record is deleted. This field has three options:
      • Delete: When the lookup record is deleted, the corresponding record in the current object is deleted.
      • Set Null: When the lookup record is deleted, the corresponding value in the current field is Set to Null.
      • None: When the lookup record is deleted, no action will be taken in the current object.

Conditions for On Delete operation:

  • On Delete option is not enabled until you click the Object Graph in any object. For more information on the Object Graph, refer the section Creating Object Graphs in MDA Objects.
  • You can see only None item in the On Delete option while applying MDA join from a:
    • Custom field in the User or Person object.
    • Custom field of any object to either User or Person object.
  • Both of these conditions are imposed to make sure that none of the records are deleted from either User or Person object.
  • By default, On Delete option in the MDA joins is selected as None from a custom field in any object and then you can change the option as required. On Delete option in the existing MDA joins is set to None from any field to either User or Person object and vice-versa.

Notes:

  • You cannot apply MDA Joins from any standard or system field.
  • You can apply MDA Joins from any custom field of data type String, GSID, SFDC ID, and email.

On Delete option.png

  • Enable self lookup: If you enable this to a field, it allows you to populate GSID from another record by looking up to one or more fields in the same standard object. Admins can use Data import lookup functionality in different connectors to ingest the correct GSID. It creates an MDA join to the GSID of the self object. This is used to create User - Manager hierarchies up to one level and ‘My team’ and ‘Portfolio view’ reports.

Note: Once you enable self lookup, you cannot disable it back.

Add Field page.png

Notes:

  • Enable self lookup:
    • You can see this checkbox only when you add fields of data type GSID.
    • If you enable self lookup, Required and Enable lookup options are disabled.
  • Currently, Gainsight does not support duplicate Display Name.
  • The idea for generating the technical field names is to simplify the formula setup on the MDA objects.
  • If you do not assign the number of Decimal Places on the Number, Currency, or Percentage type fields, the values in the field will be rounded to simple numbers.
  • While importing data into the field:
    • If an user sets a default value for the field and the source record is empty/null, then that default value will be ingested.
    • If the default value is not set and the source record is empty/null, then that record will be rejected.
    • Required constraint can only be applied on a field which does not have any null/empty values.
    • It is recommended not to apply the Required constraint on a newly added field.
  1. Add another: This is to add the current field and to open new dialog to add another field. This helps to create multiple fields in a single instance.
  2. Click ADD; then click SAVE. Object with one or more fields gets created.
  3. Once object is created, You can click Delete Object and Edit Object to delete the object and edit the object name respectively. These two options are available only for custom objects only.
  4. Click ADD FIELD to add a new field in the object.

Creating an Object Automatically Using a CSV

If a new object that needs to be created has a lot of fields, creating it manually using the Data Management user interface is a cumbersome and error prone process.

If you have a CSV data file that contains field names as headers and some data, the object creation process can be automated as below:

  • Field name is taken from the CSV header file
  • Data type of the field is auto-inferred from the CSV data file
  • Optionally, the data from the file can be imported into the object

To create an object using a CSV data file:

  1. Navigate to Administration > Operations > Data Management. Click +OBJECT.
  2. Enter the following details:
  • Object display name: The easily understandable object display name that you want to create.
  • Object name: System defined object name with a suffix of __gc.
  • Object description: Enter a description for the object being created.
  • Select Data File Upload (CSV)
  1. Click BROWSE to select the appropriate CSV file. Click NEXT.

The CSV headers are taken as is and Target Object Field Display name, Field name, and Target Object Data Type are created automatically as shown in the image below. You can change the field display name and field name. You can select a different data type, if the automatic matching is incorrect.

  1. (Optional) You can assign default values to the Target Object fields. If a null value is ingested into the field through any data ingestion channel, the null value will be replaced with the assigned default value into the field.
  2. Select Load Data to ingest data from CSV to target object. Otherwise, only the schema would be created. Once Load Data is selected, Timezone dialog appears as shown below:

  1. Click OK. You can see a Clock icon next to the Default Value check box for the Date and DateTime data types.

  1. Click the Clock icon. Select a Timezone dialog appears.

  1. Select a Timezone from the dropdown list and click Ok. This is to assign a timezone for the Date and DateTime values. These values are then converted into UTC from the selected timezone and are stored in the MDA object. If you do not select a timezone, the records are considered to be in the Gainsight Timezone. The Date and Datetime values are then converted into UTC from the Gainsight Timezone and are stored in the MDA object. For more information on Timezone standardization, refer Timezone Standardization at Gainsight.
  2. Click CREATE. Records from the CSV file will be ingested into the MDA object.

Editing a Matrix Data - Object

To edit a Matrix Data - Object:

  1. Navigate to Administration > Operations > Data Management > All Objects > [Click on an existing object] > Schema.
  1. Click on the pencil (Edit) icon to edit a particular field.

Notes:

  • Only editable fields can be edited in an object.
  • The total number of records available in the object is displayed at the top.
  • You can delete any custom object using the DELETE OBJECT button if the object has no dependencies. If there are any dependencies, you should delete the dependencies to delete the custom object.

Update/Upsert Matrix Data - Object using Update Keys

Admins can define the key field(s) that must be used on an object to update or upsert the existing records using the new Update Keys tab. This is primarily introduced to avoid updating the existing data with the wrong key fields (as it can corrupt the entire object data) and ensure that Update / Upsert operations are allowed ONLY when the valid keys are used.

To update a Matrix Data - Object:

  1. Navigate to Administration > Operations > Data Management > [Click on an existing object] > Update Keys.
  2. Drag-and-drop the desired fields from AVAILABLE KEYS to MAPPED UPDATE KEYS.
  3. Click SAVE AND VALIDATE. This defines the Update key(s).

Notes:

  • AVAILABLE KEYS: Displays all fields available in the selected object.
  • MAPPED UPDATE KEYS: After you drag-and-drop fields from AVAILABLE KEYS to MAPPED UPDATE KEYS, it reflects the key fields that you use to identify unique object records during an UPDATE/UPSERT. Once you define the Update key(s), you cannot remove all the keys from the MAPPED UPDATE KEYS column, it at least require one field in the Update Key. Therefore, we recommend you to create a new object, and experiment this feature. 

Update Keys_Mapped.gif

  • If MAPPED UPDATE KEYS do not represent a unique record, an error message is displayed when you click SAVE AND VALIDATE.
  • Once Update key(s) are defined, subsequent Update or Upsert operation in the data Ingest (S3 connector , Gainsight Bulk API, or Rules engine > Load to MDA) is allowed only when the same update/upsert keys are used. If the keys are different, the update/upsert process would fail. Therefore, exercise caution while enabling this feature for an existing object. Existing rules will fail if the update keys are different. We strongly recommend that you create a new object, and experiment with this feature.

How to Load Data into Matrix Data - Object

Once you have created a Matrix Data - Object, you can load data into the object. It is designed to load small files (under 1 MB). The purpose is to manually load a small data file and view the object data in the data browser to verify its structure.

For loading larger files, please consider other methods like loading data via Gainsight Bulk API or Gainsight S3 connector for data import.

To load data into an MDA object:

  1. Navigate to Administration > Operations > Data Management > [Select the object in which you want to load data].

  1. Click Import Data > Click Choose file to browse and select a CSV file. Optionally, you can click GENERATE CURL to generate a sample template for inserting data into the object. This sample template needs to be modified as per cURL requirements. For more information, refer to Gainsight's Load API for Matrix Data Store.
  2. Click PROCEED TO MAPPINGS; then map the CSV headers with that of the object fields. If the field names are the same in both the CSV file and the object, the mappings are done automatically. You can see a Clock icon for the Date and DateTime field mappings.
  1. Click the Clock icon. Select a Timezone dialog appears.

  1. Select a Timezone from the dropdown list and click Ok. This is to assign a timezone for the Date and DateTime values. These values are then converted into UTC from the selected timezone and are stored in the MDA object. If you do not select a timezone, the records are considered to be in the Gainsight Timezone. The Date and Datetime values are then converted into UTC from the Gainsight Timezone and are stored in the MDA object. For more information on Timezone standardization, refer Timezone Standardization at Gainsight.
  1. Click VALIDATE. If something is missing or is incorrect, during validation, you can see an error in the page as shown below. Click the link here and download the error file to view the error details. As per the error details, perform the correct field mappings or make changes to the records in the CSV file as required.

Note: Only CSV files that are less than 1 MB can be loaded.

  1. Click LOAD DATA. Records from the CSV file will be ingested into the MDA object.
  2. In the left pane, click Data. You can now see the data loaded from the CSV file into the MDA object.

Viewing Objects/Schema/Data Columns

You can select the columns that you would like to see while viewing an object or schema using the menu icon as shown in the image below.

Deleting Data from a Matrix Data - Object

To delete data from a Matrix Data - Objects:

1. Navigate to Administration > Operations > Data Management > All Objects > [Click on an existing object] > Data.

2. You can perform either of the following operations:

Delete All: Click Delete All to delete all data from a Matrix Data - Object.

Delete specific data: First filter the data that you want to delete and then click Delete to delete the filtered data.

How to Delete an Object and its Fields

Admins can now delete any unwanted or unused MDA custom object and any custom field in the MDA standard or custom objects. The specific objects and the fields can be deleted irrespective of whether they have data or not. These objects and fields can be deleted when they do not have any dependencies (it is not being used in any of the consumption areas). To delete a custom object or field, Admins should remove its dependencies first.

To delete a custom object or the custom fields:

  1. To delete a custom object:
    1. Navigate to Administration > Data Management > [Select a custom object that you want to delete].
    2. Click Delete Object. If it has any dependencies, the object cannot be deleted. It shows an error message and asks you check and remove any dependencies on this custom object.

Delete Object.gif

  1. To delete a custom field in a standard or custom object:
    1. Navigate to Administration > Data Management > [Select a standard or custom object that you want to delete fields in it].
    2. Click the Delete icon on a custom field that you want to delete. If it has any dependencies, the field cannot be deleted. It shows an error message and asks you check and remove any dependencies on this custom field.

Note: You can see the Delete icon only for the custom fields.

Delete Field.gif

  1. Click the Dependencies tab in the left pane. You can see all of the dependency features of an object and it fields. For more information, refer the section How to Check Dependencies on a Matrix Data - Object.
  2. Check all the features in the list to identify the dependencies on this object.
  3. If a feature has a dependency, click the Arrow icon on the object. It navigates you to that feature.
  4. Remove the fields from mappings in the connectors, remove the fields from a report configuration, remove the fields from a Rule setup, remove the field MDA lookups, etc.
  5. When all of the dependencies on this object are removed, you can delete a custom object and custom fields in the standard or custom objects as shown in the steps 1 and 2.

How to Check Dependencies on a Matrix Data - Object

Once the custom Matrix Data - Objects are created and then referenced in a different part of the application, we wish to restrict the Gainsight Administrators from accidentally modifying or deleting the Matrix Data - Objects and their fields as part of the object dependency tracking feature.

Currently, we are tracking the below application areas for dependency of a specific custom object and its fields:

  1. Rules
  2. Reports
  3. Relationships
  4. Data Integrations
  5. Power Lists
  6. Email Templates
  7. S3 Jobs
  8. MixPanel 2.0
  9. Segment 2.0
  10. Bulk API
  11. GS Connect
  12. Import Lookup
  13. MDA Lookup
  14. Self Lookup
  15. Update Keys
  16. Calculated Fields

To identify the dependencies on a custom object:

1. Navigate to Administration > Data Management > [Select a custom object for which you want to check dependencies].

2. Click Dependencies on the left pane to see other features that are dependent on the fields of a custom object you selected.

Dependencies.gif
  1. If you click the arrow icon on the custom object, it navigates you to the feature that has a dependency of this object. It helps you remove the dependency of the fields from the feature and then to delete the custom object and the custom fields. In the following image, the object Usage has a dependency with Bulk API.

Dependencies.png

Dropdown List and Multi Select Dropdown List

For detailed information on dropdown list and multi select dropdown list, refer to Dropdown List and Multi Select Dropdown List.

Viewing Activity Log

This section helps you see all changes made to the MDA Object.

To view the activity log:

1. Navigate to Administration > Operations > Data Management > Activity Log.

The Activity Log tab displays log details of each object. In addition, you can click the Details link to get detailed log information of the object for an operation.

Creating Formula Fields in the MDA objects

  • Calculated fields can be created using Number, Currency, and Percentage data types.
  • Number, Currency, and Percentage data type fields can be used in the formula fields while building a formula.
  • Fields and Operators can be inserted in the Formula field through the mouse click only.
  • Numeric values, functions, and advanced operators are not supported as of now.

To create a calculated field on a Matrix Data - Object:

1. Navigate to Administration > Operations > Data Management.

2. Click on the desired object for which you want to create a calculated field; then click ADD FIELD.

3. In the pop-up window, enter the following details:

  • Display Name: The display name of the field.
  • Field Name: The Field Name that is automatically generated.
  • Data Type: select Number.
  • Decimal Places: Assign the number of decimal places on the values in the field.

Note: The Calculated Field checkbox appears only if there are at least two Number fields present.

  1. Select Calculated Field; then click CREATE FORMULA. You will be navigated to the Formula Builder that has all the Field names and Operators, and the ADVANCED FORMULA option.

ADVANCED FORMULA builder helps the Admins to create complex formulas like performing arithmetic operations and case statements.

Basic arithmetic operations with constants

  • Examples : A + 10,  A - 1, A*100 , A/100, (A+B)/2

Case statements

Examples:

  • case when A>0 then 1 else 0 end
  • case when A-B>=0 then A-B else C-B end
  • case when A=B then 1 else 0 end
  • case when A is null then 0 else B * (180/7) end
  • case when (A+B+C+D) = 0 then 0 else ((E+F+G+H+I)/(A+B+C+D)*100) end

Note:

  • Ensure that the syntax is correct.
  • Validator for advanced formula is being developed.
  • Once an advanced formula field is set, reverting to a basic formula is not supported as basic formula builder does not support these operations.
  • Gainsight recommends you to write down your formula on paper. If you get it wrong while building the formula in the Formula field, you will have to start all over again. The formula can be edited from right to left using the close icon. 
  1. Click VALIDATE; then click SAVE for the formula created.
  1. Click ADD to add the calculated field to the object; then click SAVE. The calculated field has a c icon suffixed to it, as shown in the image below.
  1. (Optional) You can click on the Pencil icon corresponding with the calculated field to edit the formula, if required.
  1. Field Name can be used in a calculated field or curl command. The following image shows how Field Names look while configuring a calculated field.

The following image shows how Field Names appear when a curl command is generated. 

Creating Object Graph in MDA Objects

Object Graphs show Joins between two MDA Objects. You can get a pictorial representation of how two MDA Objects are linked to each other. This graph gives you a first hand knowledge of what exactly can happen if a record in the lookup object is deleted.

Object graphs show Joins between the current Object (Object whose Object Graph page is being viewed) and other Objects.

To view Object Graph in an Object:

  1. Navigate to Administration > Data Management > [select an Object].
  2. Click the Object Graph tab.

Object Graph_Relationship.gif

The first time you click Object Graph, the system will display a message asking you to visit the page again later. It may take a maximum of 10 minutes to load the object graph and to enable the On Delete option in the MDA Joins.

The characteristics of an Object Graph are:

  • Current object is always shown in Blue, whereas other objects to which the current object has MDA Joins with are shown in Green, as shown in the image above.
  • Object graph shows MDA joins between the objects, for up to three levels by default. Click more levels to see another three levels of MDA joins in the graph; using this you can see any number of levels of MDA joins.
  • Direction of arrow between any two objects shows the Joins from one object to another. In the image above, Activity Timeline object has a field in which MDA joins is applied to a field in the Relationship object.
  • If you click this arrow, the pair of fields that are applied with MDA joins along with direction is shown. For more information on MDA Joins, refer this MDA Joins.
  • If you observe that there are any missing MDA joins in any object graph, click resync in the object graph. It resyncs all the resources to MDA database and display all the missing MDA joins. Occurence of this issue is very rare and resync should not be applied on a regular basis. Resyncing operation takes some time depending on the number of joins between multiple objects in MDA.
  • You can see options on the top left side to move the graph in four directions and zoom in/out.
  • Color coding of the MDA joins in the bottom right corner defines the type of On Delete option configuration. For more information, refer the section Adding Custom Fields in an Object.

Supported Data Types

Data Types Description Information
String The String data type Any text. Maximum text length is 255 characters. This data type can be mapped (Join Field data type) to String, SFDCID, and Email.
Boolean The Boolean data type 0 or 1; True or False
Date The Date data type

Stores the date component.

Supported formats (Click here to expand the list)
MM-dd-yyyy
MM/dd/yyyy
yyyy-MM-dd
yyyy/MM/dd
M-dd-yyyy
M/dd/yyyy
MM-d-yyyy
MM/d/yyyy
yyyy-M-dd
yyyy-MM-d
yyyy/M/dd
yyyy/MM/d
M-d-yyyy
M/d/yyyy
MM-dd-yy
MM/dd/yy
yyyy-M-d
yyyy/M/d
yyyyMMdd
M-dd-yy
M/dd/yy
MM-d-yy
MM/d/yy
M-d-yy
M/d/yy
 
DateTime The DateTime data type

 Stores the date along with time.

Supported formats (Click here to expand the list)
M/d/yy HH:mm
M-d-yy HH:mm
MM/d/yy HH:mm
MM-d-yy HH:mm
M/dd/yy HH:mm
M-dd-yy HH:mm
MM/dd/yy HH:mm
MM-dd-yy HH:mm
M/d/yyyy HH:mm
M-d-yyyy HH:mm
MM/d/yyyy HH:mm
MM-d-yyyy HH:mm
M/dd/yyyy HH:mm
M-dd-yyyy HH:mm
MM/dd/yyyy HH:mm
MM-dd-yyyy HH:mm
M/d/yyyy HH:mm:ss
M-d-yyyy HH:mm:ss
MM/d/yyyy HH:mm:ss
MM-d-yyyy HH:mm:ss
M/dd/yyyy HH:mm:ss
M-dd-yyyy HH:mm:ss
yyyy/MM/dd HH:mm:ss
yyyy-MM-dd:HH-mm-ss
yyyy-MM-dd HH:mm:ss
yyyy-MM-dd HH-mm-ss
MM/dd/yyyy HH:mm:ss
MM-dd-yyyy HH:mm:ss
yyyy/MM/dd HH:mm:ssZ
yyyy-MM-dd HH:mm:ssZ
yyyy/MM/dd'T'HH:mm:ss
yyyy/MM/dd HH:mm:ss.S
yyyy-MM-dd'T'HH:mm:ss
yyyy-MM-dd HH:mm:ss.S
yyyy/MM/dd'T'HH:mm:ssZ
yyyy/MM/dd HH:mm:ss.SS
yyyy-MM-dd'T'HH:mm:ssZ
yyyy-MM-dd HH:mm:ss.SS
yyyy/MM/dd HH:mm:ss.SSS
yyyy-MM-dd HH:mm:ss.SSS
yyyy/MM/dd'T'HH:mm:ssSSS
yyyy-MM-dd'T'HH:mm:ssSSS
yyyy/MM/dd'T'HH:mm:ss.SSSZ
yyyy-MM-dd'T'HH:mm:ss.SSSZ
yyyy/MM/dd'T'HH:mm:ss.SSS'Z'
yyyy-MM-dd'T'HH:mm:ss.SSS'Z'
 
Number The Number data type

A whole number or number with decimal places.

Formula Support: Formulas are supported through Formula Builder; they must be set from the Tenant Management.

SFDC ID The SFDC ID data type

 
When data is being loaded to an MDA object with SFDC ID as a data type, the application checks and converts 15 digit IDs to 18 digit SFDC ID. If the SFDC ID value is not a 15 digit or an 18 digit record, data would be rejected. SFDC ID field can contain NULL.

This data type can be mapped (Join Field data type) to string and SFDCID.
GS ID   A 36 digit unique GSID is assigned for identification of each externally exposed “Object” and “Record” from Gainsight. It is assigned automatically to each record in MDA. You can import GSID of a record from one MDA object to another through data import lookup while ingesting data through Gainsight Bulk API, GS Connect, and S3 Connector. For more information, refer to Data Import Lookup.
Email The Email data type

Info

When data is being loaded to an MDA object with Email as a data type, the application validates the email ID with the following criteria.

The email ID must have:

1. At least one @ in the email address.

2. There should be at least one character before and after @

This data type can be mapped (Join Field data type) to String and Email.
Dropdown List   This data type is available for all custom fields in MDA Standard and custom objects. You can use this data type fields in other functionalities as required. For more information, refer to Dropdown List and Multi Select Dropdown List.
Multi Select Dropdown List   This data type is available for all custom fields in MDA Standard and custom objects. This is used when a user wants to store multiple values for the same record. For more information, refer to Dropdown List and Multi Select Dropdown List.
Rich Text Area  
  • This data type is available for all custom fields in MDA standard and custom objects.
  • This data type is used to support ingesting the data of all characters and basic formatting into the associated field. It is used to store large amounts of data, including comments or notes such as the Survey Comments, CTA Comments, Meeting Notes, Logging Call in Timeline, Email content in Cockpit, or Executive Summary.
  • A maximum length of 15000 characters can be defined for this field. If the length of the data to be ingested exceeds the defined length, the record will be rejected rather than trimming and ingesting the record.
  • Data can be ingested into this field through the data ingest channels like Rules Engine, S3 Connector, Gainsight Connect, and Connectors 2.0.
  • Admins can set the Rich Text Area field as a Required field.

Limitations:

  • Admins cannot assign a default value for this field.
  • This field does not support MDA Joins and update keys.
  • After data is ingested into this field, Admins can increase the maximum length of text in the field up to 15000 characters (if it was not already defined to 15000 characters) but cannot decrease it.
Currency  
  • List of currencies supported (Click here to expand the list)
    United States Dollar (USD)
    Indian Rupee (INR)
    European Currency (EUR)
    Great Britain Pound (GBP)
    Australia Dollar (AUD)
    Brazil Real (BRL)
    Canadian Dollar (CAD)
    Switzerland Franc (CHF)
    Israel Shekel (ILS)
    Mexico Peso (MXN)
    New Zealand Dollar (NZD)
    Russian Ruble (RUB)
    Chinese yuan (RMB)
     
  • The help icon for Currency Code that appears when the Currency data type is selected displays the currencies supported.

  • You can enter a number, number with thousand separator, number with currency symbol appended, or number with currency code appended. For example, 1000, $1000, 100,000, or USD1000.

  • If the data includes currency symbol/currency code, such as "USD 100", "$ 100", "100 USD", or "100 $", there should not be any space before or after the currency symbol or code.

  • Only thousand separator comma is supported. For example, 100,000.

  • If the data includes a thousand separator; for example, 10,324,342, the data should be enclosed within double quotation marks ("10,324,342"). Otherwise, it will be considered as data for the next columns.

  • You can enter a number with decimal places. For example, 110.56 $, or ₹ 55.25.

  • Formula Support: Formulas are supported through Formula Builder; they must be set from the Tenant Management.
  • Report Filters: To search for a specific value in the report, use only the number. For example, to search for $10, enter 10. 

  • Usage in Journey Orchestrator: If the user is using a currency value in the Email Template as a token, and the record value is 12, the $ symbol will not automatically appear in the email. For example, you must add the currency symbol ($<token>) before the token in the email body for the email to display as $12. 

  • A table below shows how the currency numbers will be formatted in various areas of Gainsight.
Percentage  
  • You can enter values with a percentage symbol. For example, 10%.

  • You can enter 0.1 as a value that will be automatically calculated as 10%.

  • You can enter percentage values with decimals. For example, 98.33%.

  • Formula Support: Formulas are supported through Formula Builder; they must be set from the Tenant Management.

  • Report Filters: To search for a specific value in the report, use only the number. For example, to search for 10%, enter 10. 

  • Usage in Journey Orchestrator: If the user is using a percentage value in the Email Template as a token, and the record value is 12, the % symbol will not automatically appear in the email. For example, you must add the percentage symbol (<token>%) after the token in the email body for the email to display as 12%. 

  • A table below shows how the percentage numbers will be formatted in various areas of Gainsight.
Who ID   A field of this data type can be created in any standard or custom object. This field has the ability to dynamically join with the User or Person object to identify a user or person uniquely from the current object. This helps to build reports on the current object and join the selected fields from the Person or User object.
What ID   Admins would be able to create a field of this data type in any standard or custom object from the future releases. This field has the ability to dynamically join with another standard object to fetch the source information. This helps to build reports on the current object and join the selected fields from the standard object. Currently, Gainsight does not support to create a new field of this data type.
URL   You can use this Data type to store web site addresses. You can ingest values into these data type fields that start with either http:// or https:// prefix and end with .com, .org, or any other suffix. If you try to ingest values without  the prefix or suffix, such values are not ingested.

The following table shows how the currency numbers are stored in various areas of Gainsight.

Currency type at Object level (GDM) Data Ingest Format MDA Storage Format Format in Reporting Format in Formula Fields
USD $1,000 1000 $1,000 1000
INR ₹55.25 55.25 ₹55 55.25
USD USD100 100 $100 100
USD 100$ 100 $100 100

The following table shows how the percentage numbers are stored in various areas of Gainsight.

Data Ingest Format MDA Storage Format Format in Reporting Format in Calculated Fields
0.1 0.1 10% 0.1
10% 0.1 10% 0.1
 

MDA Standard Objects

For detailed information on the MDA Standard Objects, refer Gainsight Objects.