# Delete column + Check action = (mvp of) Multiselect delivered?

**URL:** <https://community.glideapps.com/t/delete-column-check-action-mvp-of-multiselect-delivered/29203>\
**Category:** Feature Requests\
**Created:** [July 17, 2021, 7:58am UTC](https://community.glideapps.com/t/delete-column-check-action-mvp-of-multiselect-delivered/29203 "2021-07-17T07:58:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AyS\_0908](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ays_0908/32/27349_2.png) [@AyS\_0908](https://community.glideapps.com/u/AyS_0908)\
**Post date:** [July 17, 2021, 7:58am UTC](https://community.glideapps.com/t/delete-column-check-action-mvp-of-multiselect-delivered/29203/1 "2021-07-17T07:58:56Z")

</div>

Hi @Mark,

If you type the “multiselect” keyword on this forum, your computer will feel like receiving a DDoS💥: it is the dream of many Gliders for ages, it has thousands use cases (B2B, B2C | SaaS, eCommerce, Social network…), and, incidentally, it seems a common feature.

While Glide has the “check” inline list, in many cases, to have it worked properly, it requires one of the very smart aspirin-workarounds 💊 (from @Jeff_Hager, @Lucas_Pires Robert\_Petitto) which is a nightmare to setup & maintain: once we understood it (I’m still wondering if I did), for 1 multiselect field, according to the use case, it requires “10” columns, “2-3 tabs”, “2” actions… 😭

Question #1: is it right that if we had

- an action to delete a column (including user specific)
- an action triggered by the check of the inline list (to activate the “set column”)  
we would have an “mvp” of a not perfect but much easier Multiselect-like component?

Question #2: if yes, is this in your 2 months roadmap🙏🏻?

Thanks!