In this article
SmartHub provides data for Studio reports, including surveys and contact databases. Custom Data allows external data to be imported and linked.
Studio reports utilize data from SmartHub, which can include multiple data sets for corresponding widgets in the report or a single data set containing all necessary data.
These data sets can include surveys, combined surveys, and other data types depending on the metrics being analyzed, such as contact databases, panel databases, case data from Action Management, CRM data, financial data, HRIS, benchmarks, targets, and historic results.
Custom Data
Custom Data functionality allows external non-survey data to be imported into SmartHub, which can then be referenced in Studio and displayed in widgets.
This data can include current and historical revenue numbers, support ticket data, and any other information that is not stored in a survey response or contact database. Custom Data tables can also include child/parent relationships.
The data is uploaded to SmartHub as Custom Data tables and the general process includes setting up tables in SmartHub, establishing relations between tables to preserve data integrity, and simplifying schema creation by using intelligent data types identification and parsing the data in the file.
For detailed information refer to the separate SmartHub documentation
Table Relations
After defining the hub and listing the tables, it is necessary to define how the data is to be linked across the different tables.
The relationship between the tables can be one-to-many, where for each row in one table there can be many corresponding rows in the other table, or one-to-one, where for each row in one table there can be only one corresponding row in the other table.
For example, a one-to-many relationship can exist between the accounts table and the contacts table, where each account can have multiple contacts.
One to many relationship
While a one-to-one relationship can exist between a table and another table, where one table is extending the other with additional information.
One to one relationship
If the contact database was extracted from the survey, it will already be linked to the survey in a one-to-many relation and doesn't need to be defined again.
However, if the contact database is not linked to the survey, a separate relation block will be needed to tell Studio widgets how to access the data when it is located in several different tables.
To learn more about this, visit: Accessing Data Located in Several Different Tables