Using SQL to clean up CSI data

Has anyone had any luck using SQL to clean up CSI data that comes from TNEW custom forms?

We are using custom form data to collect information on our travel program participants when they register for a trip, which is great!  However, when you run a report on CSIs and export it, all the collected data comes across as one cell in excel.  I've used column splits in power query to separate everything out, but we'd love for the data to feed directly into a tableau, rather than being exported and then power queried.  I'm pretty new to SQL and completely self taught, so I didn't know if there was some way to make SQL do what the power query is doing.  The folks actually looking at and using the data don't use power query and only barely get into Tess for anything, so they currently can't get at the data themselves and certainly can't get it into a usable format.

Any advice would be appreciated! Slight smile

Thanks!

Parents
  • There's something else you can do with TNEW, which is to assign a stored procedure to receive the custom form data instead of letting TNEW create the CSI for you. This is often the cleanest option for this sort of thing; perhaps even having the SQL proc write the data into a custom table whose fields match the custom form. But, it does require some careful coding.

Reply
  • There's something else you can do with TNEW, which is to assign a stored procedure to receive the custom form data instead of letting TNEW create the CSI for you. This is often the cleanest option for this sort of thing; perhaps even having the SQL proc write the data into a custom table whose fields match the custom form. But, it does require some careful coding.

Children
No Data