Type_ahead fields: forcing user choice from the list

Classic Servoy
1

I have a standard type_ahead field which gets its data from a fairly plain and standard valuelist (I have typed in several options within the valuelist Custom Values list).

My goal is to allow the user to select one of the available choices but not allow them to edit their selection.

So, I want to force them to choose one of the set of typed in options. I have tried different settings (e.g. - Editable property on and off, valuelist Allow Empty Value flag off) but can’t seem to get to a place where the user-chosen option can’t be edited. I can achieve my goal ok with a Combo Box: the user can not edit the choice they make with a Combo Box and Editable property = false.

Is this goal achievable with a Type_Ahead field? If so, pls advise the method.

Thanks, Michael

2

I think not.
Thinking ‘ahead’ I would say that a type ahead field should be editable and as a result not what you need.

3

Hi Marcel,

I am of a different opinion here. A type_ahead field is an excellent tool for performing a user-friendly search of available selections for a given column. It provides a very rapid and efficient filtering down of available rows to select from based upon the user’s initial typing. This applies in many areas I can think of (for e.g. - Contacts, Pick Lists for Countries, Inventory SKU’s, Part #'s, Labels, etc, etc). If I have say 300 rows in total to choose from I would much rather be in a type_ahead than say a ComboBox.

I think what would be good, now that I understand it is not currently available, is something like:

  1. The default setting for a type_ahead field is as the current functionality stands;

  2. Servoy add an (optional) element level property for type_ahead fields requiring the user to choose from the available rows. If I used a type_ahead field to get say a Country (out of 200 or so) then it would be handy to ensure they chose a valid one.

Not a big deal really - I can always fire a SQL select against the chosen item or test via other app-level functions for valuelists and still use the type_ahead. I just think it would be a nice touch as an available design time element-level property. In my opinion anyway … :)

Appreciate your feedback (it is good to know that what I desire is presently not available) - I will use other methods for now.

Worth a feature request? Other community feedback?

Michael

4

I’ll add my vote.
I have used a Combo Box to achieve this effect but would prefer the reducing list that we get with a TypeAhead. Another difference - with the Combo Box, each key stroke triggers the OnDataChange form method, which interrupts the typeAhead effect.

5

yes you must use a combobox or use a different type that is the real value
So make a valuelist that stores an integer but displays a string. Then a user must make the right selection because something else can’t be mapped to a integer.

6

Johan,

Thanks, and appreciate your feedback. I am already using methodology as you suggest (string display, integer as the foreign key or referenced field).

My suggestion is to do with the user benefit (for ease of selection) the typeahead field provides. A combo box works ok but simply doesn’t provide the elegant filtering and ease of use the typeahead field does in certain data sets.

If you do come up with a solution where we can use the typeahead instead of the Combo Box in the stated scenario, please consider this as a feature request.

Best,

Michael

7

And a related wish, could there be a way to disable the triggering of the OnDataChange event after each key-stroke in a Combo field, so it behaves like data entry in other fields.