I'm afraid that the values are stored as numeric results so currently you would need to add a key, perhaps a bit like I have done on the last screenshot of this article: A step-by-step example of how to configure the "Autosearch" functionality for End Users (includes some reporting advice)
If you prefer, you could change the surveys so that users pick from a reference list rather than from allowed values on the attributes for each question. However if you do this then you lose the benefit of having numerical values such as "we were rated 98 out of a possible 100 on Q1 this month".
There is a problem record raised for this which is Problem 5554 "Int16 attributes with Allowed Values display the number instead of the text in queries in Web Access". Please could you raise this with your Support provider as a support incident so they can link you to the problem record.
Did this progress or go anywhere?
Just tried in 7.7.1 and I'm seeing the same behaviour mentioned in the original post?
You could also use calculations to turn a number into text.
Another solution (and actually better practice) would be to replace the Int16 attributes with a reference/ordered list to store the survey answers. The Int16 "Allowed Values" functionality has a lot of limitations like this and we generally don't recommend it these days. Using a related object will allow the same functionality when filling out the survey but give much better options for reporting on the data later.
Of course if you're already using surveys you'd need to migrate the existing answer data which might not be so easy...
The Int16 "Allowed Values" functionality has a lot of limitations like this and we generally don't recommend it these days.
Hadn't heard that before. I really should be using reference lists more, the Int16's are just so easy.