The lookup element has replaced many of our Option List elements with more capability and ease of use. It would be great if we could have the same ability to use an element like the lookup element and be able to select multiple options. Looking for multi-select element capabilities with the lookup element setup.
Hey Dave, happy to hear that the Lookup Element has been able to replace many of your previous elements. Can you tell us more about the specific use case for a "multi-select" lookup element? How would you expect to use it as both the field user and also the data manager regarding any integrations or post-processing?
Hi Jonathan. As a field user I would want to be able to see 1-3 columns of the lookup table and be able to select as many of the rows as needed. As a data manager I would want to have a single value from that row returned for each selection and have the selections delimited in some way (similar to existing multi-select element). The thought is to replace the multi-select elements we have in use currently with a lookup style element. Main objectives for field users would be to put more information in their hands through the app. As a data manager I would want to know just the "key_value" for the row(s) they selected.
Thanks for the feedback Dave. While not ideal, you may be able to achieve your desired result today by setting the label for your option list to a delimited string. As for the potential of a multi-select lookup element, I'd imagine that we would maintain the same data structure that we use for the current lookup element which is that the row selected is an object. If multiple rows were to be selected, the data model would most likely then be an array of objects and not a simple delimited string.
Regardless, this type of insight is very helpful for our team to understand how current features are being used and what types of challenges remain.
Appreciate the share Dave!
Please sign in to leave a comment.