In my form I have a TEXT_FIELD linked to a value list made of integers.
When I use the field, the drop-down doesn’t print all the values, when you start to type a number it doesn’t filter the list, you can’t validate your choice by pressing the ‘Enter’ key (you have to click outside the field) and finally when you enter a number over 999 and validate it, it adds a ‘,’ for the thousands (e.g. ‘1222’ will become ‘1,222’).
However the value used by the application (in my case, to filter a list of records) is correct (without ‘,’) and filters well. Moreover, if I assign another value list to the text_field (without changing anything else) the drop-down list works perfectly)
I can’t use this format because I need to be able to enter 1 or 2 digit numbers. Using this format put the small numbers in red and raises error when I use them.
Moreover it doesn’t solve my problem of ‘Enter’ key validation and suggestions filter
Your dataprovider appears to be text, not integer. Setting the format to ##### for a text-dataprovider means: “must be exactly 5 number-characters long”. That’s why it doesn’t let you save values of 1 or 2 digits.
What happens if you set the default integerformat to #### on the Locale-tab of your client preferences?
Oops yes it should be TYPE_AHEAD. But I probably changed it because even with TYPE_AHEAD the suggestions filter is not working
I don’t want to change the type to INTEGER because in the future we might add letters in this numbers. So I would like to process them as Strings (even if the ordering is not good).
I’m still working on this problem and I’ve noticed a difference between this filter and the others I use. In this one, the value list used is made using a column of type “servoy seq”.
In the database it is stored as normal integer. So maybe Servoy automatically provides a format for “servoy seq” values and/or it disable the TYPE_AHEAD property?
After, I’ve checked with my other filters, and they are configured exactly the same.
