CSV pulling from all columns, how do I limit?

I have a table view that shows the results of a form that allows users to create a filter query.

I need to be able to export the resulting data, shown in the table view. I tried an action with producing a CSV. BUT, it brought in ALL the columns from the slice used on the form view gathering the criteria. There are columns used for filtering that can NOT be displayed in the resulting export. They don’t show on the detail view you access via the table.

How can I limit the columns in the CSV? Or is there another way to produce of list of these filtered records with only the columns I want displayed?

Thanks.

I do this with workflow reports… I create a table that I call the “report builder” here they can select a dataset/template, then put filtering requirements. This can be shown in a dashboard view, and can trigger the excel/PDF file to be emailed to them. I haven’t played with it, but I’ve been considering adding in the functionality to “subscribe to the report” and receive it on a schedule.

3 Likes

Export CSV is not a row-level action, I dont think we can achieve your goals. To download only the selected fields, create slice and then associate CSV export action to that slice, and display action icon to your app user, but I reckon this is not what you want.

As @Grant_Stead said, I woud go with Workflow to send excel files to the users where the selected columns are only displayed in the final output attachment in the form of excel, rather than downloading.

2 Likes

To limit the columns that are included with your CSV download, you need to create a SLICE that only contains the columns you wish to include.


It’s with this same slice that you can also restrict the records that are being output as well - you just have to build the formula to do such.

@Grant_Stead suggestion about creating a “Report builder” table - where people can enter any criteria you’ve built support for to limit the data of the report - is a solid one.

Think about it this way: you want people to be able to enter data, and have the app use that data to restrict records for your report. You’ll need a place to store that data, if you’re app is going to use it… it has to be present somewhere - that is the Report Builder table.

It’s from the Report Builder table that your workflow then generates the appropriate file.

1 Like