lmaloney opened a new issue #19426:
URL: https://github.com/apache/superset/issues/19426


   ### Discussed in https://github.com/apache/superset/discussions/18247
   
   <div type='discussions-op-text'>
   
   <sup>Originally posted by **cccs-rc** February  1, 2022</sup>
   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](https://github.com/apache/superset/pull/16510/files). However, our users 
rely heavily on that "Select All" functionality, so we're hoping this can be 
brought back in some form or fashion. 
   
   <img 
src="https://user-images.githubusercontent.com/62034438/152042546-27a0095a-7e9e-448b-9f12-2f8e98698ac7.png";
 width="300">
   
   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! 
   </div>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to