Unable to "hide all" features for a Table Component. Forced to manually select each field

💬 Feature Requests
1

ReTool select all table component feature request
ReTool select all table component feature request798×619 53.3 KB

I am trying to modify a table component. By default when I pull in a table for a selected query source, the table shows all the columns. I then need to modify the table to only show a few columns, followed by performing Group By operations to show aggregated numbers.

However, ReTool doesn't allow me to "select all" fields and make them hidden, so that I can then un-select the three columns I need to show.

I am forced to manually select all columns to hide them. Can we introduce a simple "select all" feature that allows me to select all columns at once, so that I can perform visual operations on them with a single click?

The workaround I do is to create distinct code components and create tables from them. But it would be easier to have a single code component, and have multiple tables/charts pulling in from the same code where I can select each features to show in each chart.

Thanks,
Mahesh S.

P.S.:- If this feature already exists and I've managed to miss it, please let me know.

2 Likes
3

+1

4

Hey @lindakwoo , @Tess , @Darren :wave:

+1 to this feature request — having a "Select All Columns" option for visibility settings in the table component would be a massive time-saver. Currently, hiding dozens of columns one by one is both tedious and error-prone, especially when working with wide datasets.

This kind of bulk operation would not only help streamline workflows, but also make Retool more user-friendly for both technical and non-technical users. A simple toggle like “Select All” with the ability to unhide only the needed columns would greatly improve productivity when setting up dashboards or reports.

It’s a small UX tweak, but one that would have a big impact across all projects, especially when reusing a single data source across multiple tables or charts. Hope this can be considered for the roadmap!

5

Thanks for the context, everybody! I can see how this would make for a nice QoL feature in certain scenarios and have documented your feedback internally. :+1: That said, it may not be something that we prioritize in the immediate future. As soon as we do, though, I'll provide an update here.

In the meantime, would it save you time to simply clear all the default columns and recreate the ones you need?