There are certain files in the AWS S3 Export that are better suited for CVS format and others that are better suited for JSON or XML format. I would like to request and option to have the integration allow for file type selection for each file, not just file type selection for all files.

Use Case: For all structured files coming out of Gainsight PX (event, engagement, feature matches) a CSV file is a bit more manageable with automated processing tools like Talend as it allows for the entire file to be inserted into an existing table structure. 

However, when you get into some of the more “unstructured” or “dynamic” files, we run into issues where the CSV format does not allow for nested data structures or is now less desirable as column structure and order is no longer finite.

The Request: I am asking that the AWS S3 Export Integration allow for a file type to be selected for each individual file as opposed to a file type being selected for all files included in the export. This would allow for more flexibility of data management outside of Gainsight PX which is what the integration is intended. 

While the Gainsight Rest API may be a backup  for the nested data need, the standardization of data processing in with an Integration is more manageable for end users like myself. Long term data extraction can be cumbersome for end users like myself to manage when there are millions of records to be extracted. Which again, is why the integration was likely created.