This content has been marked as final. Show 4 replies
I'm glad to see that I'm the only one with this problem...
Would anyone care to share how they managed to avoid this problem with numerical autosuggest?
Just change your returntype as "string" and that will do..
Thanks for your reply.
You mean the 'returntype' in the cffunction definition? If I do that, it breaks to whole autosuggest and it doesn't work anymore even for alphabetical autosuggests.
If you meant something else, please explain it to me because this is a real problem.
I read in a blog a comment by someone who appeared to be working for adobe and he said that they were going to put it in their bugtracker.
Here's the blog's URL that talks about this problem.
This problem seems so important and at the same time, almost nobody seems to be talking about it.
i have never needed to use an autosuggest with numeric values, so not
sure if any of this works, but see if this helps you as a work-around
until the bug is fixed by Adobe:
1) use your db's equivalent of CAST() function to convert your numeric
value to a string in the query that populates your autosuggest field
2) use your db's string concatenation function/syntax to add a space [or
some other character] in front of your numeric values to turn them into
strings (don't forget to trim that character from the autosuggest field
value when the form is submitted)