# Limits of Multi-Select element - Fallbacks and Binding of values

**URL:** <https://community.weweb.io/t/limits-of-multi-select-element-fallbacks-and-binding-of-values/4147>\
**Category:** How do I?\
**Created:** [September 1, 2023, 9:29am UTC](https://community.weweb.io/t/limits-of-multi-select-element-fallbacks-and-binding-of-values/4147 "2023-09-01T09:29:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 1, 2023, 9:29am UTC](https://community.weweb.io/t/limits-of-multi-select-element-fallbacks-and-binding-of-values/4147/1 "2023-09-01T09:29:58Z")

</div>

Is there an easy way without hacking the elements with CSS/JS to change this “No results found” value? My app is supposed to be used by elder ladies sitting in the offices in Slovakia 😃

_Edit: Would be nice to be able to have that as a Free Layout as well \<3_

 ![Screenshot 2023-09-01 at 11.28.06](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/4/4adf0e778d6583511de9abbfee6b4e71171be902.png)

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 1, 2023, 9:38am UTC](https://community.weweb.io/t/limits-of-multi-select-element-fallbacks-and-binding-of-values/4147/2 "2023-09-01T09:38:35Z")

</div>

I’m hitting the limits of these selects a little. It would also be nice if we could combine values in the label field, so it’s searchable by a combination.

For example [‘name’]+[‘model’] or make it bindable. So I could search Ford Focus 2023 instead of Ford only. I know it could be done by joining the fields before - eg. transforming the data, but that’s so much work for something like this 😃

 ![Screenshot 2023-09-01 at 11.36.32](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/0/0922ac16b11f244ec76613c6a228aa6dd001ff93.png)

---

<div class="post-metadata">

**Author:** ![Alexis](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/alexis/32/13248_2.png) [@Alexis](https://community.weweb.io/u/Alexis)\
**Post date:** [September 1, 2023, 1:14pm UTC](https://community.weweb.io/t/limits-of-multi-select-element-fallbacks-and-binding-of-values/4147/3 "2023-09-01T13:14:37Z")

</div>

For now I don’t think so but I will create a product ticket so we can add a property to set the text (and an element for the free layout mode) 🙂

> I’m hitting the limits of these selects a little

Its an annoying limit we have for every elements using the property path pattern. We are working on the best solution to provide transform capabilities. I personally developed two different prototype, one where we replace every path selector with a custom formula, and one where we add a new transform step along side of filter and sort, still exploring the best solution, but it will be handled for sure! 🙂

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 1, 2023, 1:27pm UTC](https://community.weweb.io/t/limits-of-multi-select-element-fallbacks-and-binding-of-values/4147/4 "2023-09-01T13:27:09Z")

</div>

Lovely news @Alexis, thanks for your answer)