Replies: 7 comments 1 reply
-
I agree. I just installed the current docker image for SuperSet, and Select All is missing, and it's painful! :( |
Beta Was this translation helpful? Give feedback.
-
Why was this feature removed? |
Beta Was this translation helpful? Give feedback.
-
Hi! Thanks for the feedback. To be honest I am not sure why this change happened, but I agree that there are multiple cases in which this would be super useful. I am going to look into though and add it to the tasks. |
Beta Was this translation helpful? Give feedback.
-
I just created a PR to add this feature : #19979 |
Beta Was this translation helpful? Give feedback.
-
hello guys! this issue touched me a lot too.
|
Beta Was this translation helpful? Give feedback.
-
It seems this feature is still lacking from the chart creation in v3.1.1, 2 years later. It's particularly painful when you want to add a table chart with many columns. @cccs-RyanK PR has been closed because the feature was being worked internally, but it doesn't seem to be the case anymore. |
Beta Was this translation helpful? Give feedback.
-
I am also having big pain creating a table chart with many columns. I have to add each manually and takes a lot of time. What is the reason for delaying this feature so long? |
Beta Was this translation helpful? Give feedback.
-
Hi all,
Having recently deployed 1.4, we've discovered that the "Select All" option (pictured below as seen in 1.3) was removed from column SelectControl in the Explore view. It appears to have been a conscious decision made during the work done for this SelectControl refactoring PR. However, our users rely heavily on that "Select All" functionality, so we're hoping this can be brought back in some form or fashion.
Without a "Select All" functionality, users are forced to manually select all the fields they wish to include in a chart. This doesn't scale well when dealing with datasets that have 100+ columns. Our users often want to view such data sets in table charts. While they may ultimately decide to pare the number of fields down to those that are most relevant to their use cases, when users are initially developing charts, it can be critical for them to be able to easily view all the fields/data available in order to identify which fields are most relevant.
Our users rely on this functionality so heavily that we've already jammed it back into our fork, so we've seen that things can get a little weird in the UI with the new functionality and a Select All option (e.g., when selected fields are moved to the top of the column list, where should the "Select All" button go?). We're hoping we can come up with a design that will allow us to keep the "Select All" functionality while maintaining good UX.
We're happy to do the work and put in a PR if we can get some insight into what criteria the design should meet.
Any thoughts/insight would be much appreciated!
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions