Select multiple fields to move to a folder or hide

While creating and editing datasets, we typically join a fact table to many dimensions. Many of the fields of those dimensions are not needed in the view for the dashboard creator, or we need to move those fields into folders. There seems to be no way to multi-select these fields and move them into folders, or hide them. This ends up being a single click on each field (which can be over 100 fields), just to move them into a folder, or hide them. Why isn’t there some sort of “click-Shift Button” functionality to select more than one at a time? This is a HUGE time waster when managing dozens of datasets.

Hi @oanielsen

what typ of datasource do you use?

At least if you reuse a dataset you only have to do it once.

BR

We use a redshift table as the data source. Unfortunately, the table we use holds approximately 150 different values. In this case, its “goals” for doing “Actuals VS Goals” calculations Each of these “goals” are not needed for each fact table we join to it. We need a curated set of goals for each fact table. So, each time we join to this goals table, I have to do a single click on each goal that is not needed, and hide them. Its quite painful. :slight_smile:

Hi @oanielsen - If it is a relational data source, then you can use custom sql and select the require fields and bring those fields to QuickSight.

This is just a work around or else yes manually you have to add to excluded list.

Regards - Sanjeeb

1 Like

Understood, but why can’t there be a way to select multiple fields at once when trying to move them to the excluded list? Using “click-shift” or “click-control” is how nearly all modern multi-select functionality works when selecting from a list.

1 Like

Hi @oanielsen - This is a good observation and can be added a feature request.

Hi @ErikG - Can you please help on this?

Regards - Sanjeeb

@Sanjeeb2022 you already described my best practice “Do not use Select *” :wink:

@oanielsen “click-ctrl” works but as you said you have to click every single field.

1 Like

Agree with @ErikG . It is always advisable to bring the require fields that is use for reporting, however in reality for easy use, users are put select * to make the things simpler. We should have one easy approach to add those unused fields in exclusion list as well :slight_smile:

Regards - Sanjeeb

1 Like