Hi..!

Quoting from your documentation:

"The only limitation is that the only possible editor input type for those columns is the single-value selectbox, since the options are limited with respect to what the remote table contains."

Please can you help me and others understand what is this limitation based on? I mean, for the other input types, sure this is obvious, but for multi-value selectbox?

At least for me it's hard to see the big difference in this context between single and multiple value. Makes things a bit more complex yes, but can't be impossible?

I bet a large number of users would very much like (even need) to use foreign keys with multi-value selectboxes, this would be a solution for so many different scenarios.

Let's say I have configured a foreign table relation where I could choose several options when ordering a new car, for example: alloy wheels, tinted windows, parking camera, premium audio system. If only there was the possibility of using multi-value selectbox... with the current limitation I only can choose one option to the order.

Ok, to be fair, in this particular example we probably would choose to set up separate foreign key columns or just predefined value lists for selecting wheels, audio, camera etc... but often this is not something that can be done and only one column would be preferred.

A far better example would be when multiple items (similar or different) need to be selected to the order and the total number of selected items can vary greatly.

So, is this something you just haven't implemented yet or are there some actual big problems or technical limitations preventing it..? In the latter case, I really hope you could take the time to consider could there be a way to accomplish this functionality somehow so it could make it to your feature roadmap.

Thank you, as always.
Alex