We are Experiencing the same issue since we upgraded to Qlik Sense 3.0.1. from 2.3. I found one link regarding an issue with the Treemap being responsible however we are not using that object. I know that this does not help you, but YES, you are not alone and I have also been looking for a solution.
Response from Qlik Support
The behaviour is due to bug QLIK-61990, which will be fixed for good in 3.2
3.1 doesn't completely fix the issue, but it features an easter egg to temporarily disable the function (visual search within objects) that cause the problem.
These are the steps:
- stop the engine service
- edit the Settings.ini in C:\ProgramData\Qlik\Sense\Engine so that it reads like this (important: there's an empty line at the end):
- start the service again.
When searching, objects will not be shown visually, but you'll still have the chance to pick the searched values.