We get back results if the word is first in the string or preceded by a space, but not when preceded by other characters like '/', '\', '-', etc. This behaviour is confusing for most casual or even regular users.
Some alternatives:
-Always present search results that also match your input after one of those common characters
-Give the chance of making the wildcard search the default app-wide (Maybe make this a variable in the load script)
-Adding a checkbox in the dimension properties of the filter pane so we can allow the automatic wildcard search for a specific field. Although this could add confusion if the selections bar doesn't behave the same way.
We have a customer very annoyed by this fact. We are migrating from view to sense and when you have thousands of standard users expecting the search function to behave as is did in View (with no * required) and now they all need to add a * when searching columns it really creates a problem.
We have the same complaint from a client who had just been migrated to SaaS, will this issue be addressed in the future? Has anyone come across a work around in the meanwhile? Qlik Cloud
