New Idea
SQL Interface to build Reports - OR - Use the Rule Engine from Journey Orchestrator for Report creation
You know you're writing too many Gainsight Reports when you start to dream of ways to improve the process. As an former database engineer, I have become used to SQL, joins, unions, views, temp tables, and exporting to CSV file (not excel). These are many of the things that would be very handy while creating reports within Gainsight. Being able to join 2 tables using a common column, or save output in a temporary table and create a report based off it - is a feature that many Gainsight users would welcome. Many of these features are already available within the Rules engine in Journey Orchestrator - but not available within the report tool.
For many reports, I have to export the output to a file, edit the file (if needed), load it into a database, run a query to extract only the rows needed, and perform any calculations on the fly, then import the result into excel to provide management.
For other reports, I may have to export 2 or more tables, then use a database to join them together.
For many reports, I have to export the output to a file, edit the file (if needed), load it into a database, run a query to extract only the rows needed, and perform any calculations on the fly, then import the result into excel to provide management.
For other reports, I may have to export 2 or more tables, then use a database to join them together.