Export Filtered Data

Ask for Help
1

Hi there,

I’m looking to export filtered table data on a page.

The issue I’m facing is that the export functionality only exports the full table (from the backend) and not the filtered data that’s shown on the UI.

Can anyone provide exact steps,

Cheers
Mark

2

In your CSV action you can choose the source, meaning the data you’re to going to export as CSV. Even if you have filters applied, they are only applied in the front end, the entire data set will be downloaded as a CSV.

You would need, in your glide table, to add a query column, and filter only the desired element, the in the CSV action, use your query as source. Then the CSV will only have data from the query.

If it’s not a static export, meaning your criteria for the export change in time, you will need to use a custom filter. Robert Petitto made some great videos about it, Ill see if I can find them.

1 Like
3

It’s most likely not a “static export” per Lucas’ definition above, since you allow users to filter them on the front end. You can get started with this.

1 Like
4

did you manage to do it @Mark_Bailey ? I so, could I get help from you?

I am looking to do the same with my app. My problem is that my data base is large and a lot of filters.

5

How many filters are we talking about here?

6

I am using 6 filters, created with the in-app functionality

7

In-app filtering only applies to the collection itself on the front end. You can’t use it to filter anything in the back end for export. You would have to build your own custom filters.

1 Like
8

As long as you build your custom filter correctly, you will be able to generate a CSV through a query with those filters, and allow the user to download that file.

2 Likes
9

@ThinhDinh Recently I was unsuccessful with trying to export a subset of data stored in a Big Table. Do you know if that’s a known limitation?

10

image
image768×744 79.4 KB

I haven’t found anything that can cause the problem. Does it not export at all or there’s missing data?

11

What method were you using?

The Generate CSV integration isn’t supported with Big Tables, but there are other approaches that can be used. Three separate methods that I’ve had success with:

  • The traditional joined list via a relation/query. Works okay but could be limited to 100 rows depending on any computed column types involved.
  • A joined list of joined lists, then use JavaScript to generate the CSV.
  • Use the Glide API to run a query from Make, then generate the CSV on the Make side. This is a pretty robust method, but can only be used if you are filtering on non-computed columns. I helped Jack make a video that describes this method, see below:
2 Likes
12

Do you have detailed instructions for setting up scenarios on Make.com? I watched a video, but I didn’t quite understand how to set up scenarios in Make.com

13

That video that I linked to in my previous reply describes how it’s done. Where exactly did you get stuck?

Here is a screen shot of one of my scenarios that does a CSV export:

CleanShot 2024-08-03 at 17.45.03@2x
CleanShot 2024-08-03 at 17.45.03@2x2694×960 90.9 KB

The essential pieces of it are:

  • The webhook that comes from Glide and contains the Query JSON, and what ever other information is required. In my case, the email address of the user that triggered the action in Glide.
  • A HTTP module to Query the Big Table via the API
  • An Iterator to process the returned rows one by one
  • A CSV module to map the columns to appropriate CSV fields
  • An Array Aggregator to bundle the CSV rows up into a single text string
  • And then some sort of email module to send the CSV to the user (in my case I’m using Office365)
2 Likes