# Issue Recognizing Selections in Multiselect Variable

**URL:** <https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483>\
**Category:** Ask us anything\
**Created:** [April 30, 2022, 5:11pm UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483 "2022-04-30T17:11:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kyanaloe](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kyanaloe/32/1076_2.png) [@kyanaloe](https://community.weweb.io/u/kyanaloe)\
**Post date:** [April 30, 2022, 5:11pm UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483/1 "2022-04-30T17:11:21Z")

</div>

I am having an issue where weweb doesn’t seem to be recognizing that I have made selections with a multiselect element.

 ![multiselect issue](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/1X/6d76d4c25af45a642256cb5f5de53f6669aa7e12.png)

Any ideas?

---

<div class="post-metadata">

**Author:** ![kyanaloe](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kyanaloe/32/1076_2.png) [@kyanaloe](https://community.weweb.io/u/kyanaloe)\
**Post date:** [April 30, 2022, 10:12pm UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483/2 "2022-04-30T22:12:08Z")

</div>

This is also happening on short answer text inputs. The variable value is not being conveyed properly to the formula for filtering, it seems.

Here is a loom with an explanation:

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [May 2, 2022, 9:02am UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483/3 "2022-05-02T09:02:48Z")

</div>

Hi @kyanaloe, thanks for this. Not sure what’s going on here. I’ll share with the devs and get back to you asap.

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [May 2, 2022, 12:06pm UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483/4 "2022-05-02T12:06:51Z")

</div>

Hi again! It’s fixed 🙂

---

<div class="post-metadata">

**Author:** ![kyanaloe](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/kyanaloe/32/1076_2.png) [@kyanaloe](https://community.weweb.io/u/kyanaloe)\
**Post date:** [May 2, 2022, 12:08pm UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483/5 "2022-05-02T12:08:41Z")

</div>

Just out of curiosity, are you able to share any more about what was going wrong?

---

<div class="post-metadata">

**Author:** ![aurelie](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/aurelie/32/13249_2.png) [@aurelie](https://community.weweb.io/u/aurelie)\
**Post date:** [May 2, 2022, 12:42pm UTC](https://community.weweb.io/t/issue-recognizing-selections-in-multiselect-variable/483/6 "2022-05-02T12:42:47Z")

</div>

Hi @kyanaloe, it’s an internal bug about how we handle variables.  
We were loosing reactivity (the fact that the value auto-update) when we were dealing with element variable.  
This is why value were correct in same places but not in others.  
It is now fixed 🙂