In plumsail forms, there is a difference between a lookup and a choice field.
When you get into a lookup field, you have to explicitly select the "dropdown arrow" to see the possible choices. By default you end up in a kind of search window.
Is it possible to make this behavior of a lookup field equal to that of a choice field?
Hi @bartplessers,
I'm afraid changing field appearance like this is currently not supported. The difference in appearance is deliberate, since a lookup may have an enormous amount of options.
Hi Ilia,
I agree.
But let's be honest: in most cases a lookup is used because it is easy to add or remove options. You do not need "design" rights to modify the options of the main list, only "contribute" rights on the source list.
So in most cases people are using lookup fields because it's much more maintainable, not beccause they have large lists.
However, a lookup field in a Plumsail form takes much more effort to select your choice. Especially on a mobile device: once you entered the (lookup)field, the keyboard appears, and this is confusing. Even on a non-mobile view, if you "tab" around your form, entering a lookupfield takes more actions to select your desired option.
So maybe it can be considered to add a configuration setting to a lookupfield that you can instruct it to behave as a choice field?
I think a lot of users can benefit from this because it makes the form much more user-friendly.
kind regards,
bartplessers