Data Spaces provide a virtual object structure that exposes a more consumable way to use data in Reporting and the Rules Engine. A Data Space is a collection of different objects with their lookup relations brought into one view. An administrator with the help of Data Spaces flattens the object hierarchy and makes it much easier and simpler for creating a report or a rule. An administrator no longer has to remember the object names and their lookups (object structure) each time they configure a rule, report, or relationship. In addition, Data Spaces provides the capability to use multiple related objects in one report or rule. For those familiar with databases, Data Spaces are comparable to Views in a relational database.
For example, for reporting and rules engine related consumption, an administrator does not have to remember that there are five different objects that fall under Survey, or that a Success Plan is stored in the CTA Group object. The fields belonging to a particular object are presented in a list view.
Data Spaces allows an administrator to dig deeper into SFDC objects. This flexibility was unavailable before the introduction of Data Spaces.
The benefits of using a Data Space include the following:
- While creating a report or a rule, it reduces the complexity of going through all object(s) and underlying objects, and their numerous fields. The fields are already present in the Data Space.
- Whenever a Relationship Type is created, we automatically create a default Data Space for all the directly linked objects and for the relationship type.
- For example, if the Relationship Type name is “Sample Relationship Type”, a Data Space called “Sample Relationship Type” is created. Apart from this, if the Relationship Type name “Sample Relationship Type” has the CTA Group object (CTA Group contains Success Plans) as a linked object, then we automatically create a Data Space called “Sample Relationship Type Success Plans”.
- In the image below, if you select CSTask as the base object, the Data Space that you create can include access to Call To Action, Account, CSM, Role, and Owner objects and their fields. This flexibility was unavailable before the introduction of Data Spaces.
Four Out-of-the-Box Data Spaces are available at Administration > Operations > Data Spaces:
- GS Tasks
- Success Plans
- NPS Text Analytics
- CTAs: enables you to build reports on risk CTAs by revenue band, or CTAs by customer stage, for example
- CS Tasks: similar data is available at the task level
- CTA Groups: enables you to report on Success Plan objectives and tasks more easily
- NPS Text Analytics: enables you to build reports for NPS Analytics
Note: You cannot edit or delete these Data Spaces.
Two Default Data Spaces are available at Administration > Operations > Data Spaces:
- Survey Dataspace
- Survey Question Dataspace
Note: You can copy these Data Spaces using "Save as" and then add fields as needed.
Following table lists the Data space types and details:
|Delete||Clone||Edit Name & Description||Add custom fields|
|Default||No for system fields||Yes||Yes||Yes|
Important Gainsight has recently introduced a new feature called Data Designer, which has more advanced capabilities than this version of Data Spaces. Gainsight strongly recommends you to use Data Designer as a primary method for creating Data Spaces. For more information on Data Designer, refer Data Designer Overview.
- Data Spaces are available for use with Salesforce objects and not yet available for use with MDA objects.
- You can traverse up to five levels only. For example, if you are selecting CSTask as the base object, you can traverse only up to the Role object as shown in the diagram above.
- You cannot link two unrelated objects. For example, if you select the Usage object, you will not be able to get fields from the Survey object.
- If you select the Account object as the base object, you cannot obtain fields from the CSTask or the Call To Action object.
- Date fields cannot be dropped into data space filters
Example Use Cases
- Opportunity Product, Opportunity and Account
- Journey Orchestrator User lookups
- Role Hierarchy/Regional Reporting (up to 5 levels)
- CS Task, CTAs, CTA Group, CustomerInfo, Account
- Associated records on CTA or CSTask
- Leverage custom objects from other applications with fields on our objects
- 4 Out-of-the-Box Data Spaces(cannot be modified)
- CTAs and CSTasks and CTA Groups (Success Plans)