S3 Connector file ingest without header row
The field mapping for an S3 Connector file ingest currently requires the first row of the csv to be a header row with the column name for mapping. It would be great if there was an option to uncheck header row and just map on column number.
Use Case: From our data warehouse we have to write custom SQL for every unload to S3 in order to add this header row. Our BI tool allows for scheduling report output to S3 but does not include a header row. Maintenance would be drastically reduced if had this functionality from Gainsight so that we could manage data pushes from a report instead of custom SQL.
Use Case: From our data warehouse we have to write custom SQL for every unload to S3 in order to add this header row. Our BI tool allows for scheduling report output to S3 but does not include a header row. Maintenance would be drastically reduced if had this functionality from Gainsight so that we could manage data pushes from a report instead of custom SQL.