Page 1 of 1

Typeahead fields don't work for the second word in search

PostPosted: Tue Apr 25, 2017 2:49 pm
by aurobindo.parida
I am using servoy version 7.4.3 (Not sure if this is the case with other versions)
The typeahead fields in servoy don't really take into account the second word in search string.

For example if I am searching "Australian Post", The list shows all the values having "Australia" as their first word.
But as I continue to type it does not work. When I type the second word that is "Post", It just sticks there not further filtering.

All of this is related to web clients.

Are there any solutions to this ?
Thanks in advance.

Re: Typeahead fields don't work for the second word in searc

PostPosted: Tue Apr 25, 2017 5:24 pm
by sean
Hi

I can confirm that this is working fine for all client types.
(at least in 8.1.2 - I didn't try your version)

Can you share the valuelist definition? Is it a regular table-based valuelist?

Is "Australian Post" coming from the same columns ? i.e. you are not using a second display column in the type-ahead definition.

Do you have a screenshot of the problem ?

Re: Typeahead fields don't work for the second word in searc

PostPosted: Tue Apr 25, 2017 9:10 pm
by aurobindo.parida
Thank you Sean,

I am attaching the screengrab of the typeahead field (on web client) as well as the value list.
Please have a look.

Thanks

Re: Typeahead fields don't work for the second word in searc

PostPosted: Wed Apr 26, 2017 4:08 pm
by sean
Yes, that certainly looks unusual. As I said, I have not tested it w/ 7.x
So I recommend that you file a case at https://support.servoy.com, including a reproducible example solution.
Please share your case-id in this ticket, so others who are interested can follow.
Thanks!

Re: Typeahead fields don't work for the second word in searc

PostPosted: Thu Apr 27, 2017 10:47 am
by aurobindo.parida
Thanks,

Further testing it I found it happening when the data provider is an integer.
And it is happening only on 7.4.3 version.
I think this has already been fixed on 7.4.9 as it was not reproducible there.

However I have filed a case on this - https://support.servoy.com/browse/SVY-11087