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

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 :smiley:

Edit: Would be nice to be able to have that as a Free Layout as well <3

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 :smiley:

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) :slight_smile:

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! :slight_smile:

3 Likes

Lovely news @Alexis, thanks for your answer)