Skip to main content

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

Qlik Sense Search Assistance - full text / fuzzy etc

AlexOmetis
Partner Ambassador
Partner Ambassador

Qlik Sense Search Assistance - full text / fuzzy etc

We've had some staff at a customer finding it non-intuitive how Qlik Sense search works. Some people expect it to be a Google-like experience which is more based around whole-word and multiple matches - which is pretty much what Qlik does - but others expect it to be more like Excel which will locate the search term anywhere in a string - these users are left puzzled.

Sharing the very useful Qlik Sense Cheat Sheet version 2.0 - Qlik Community - 1667455 can only get so far as it's not easy for users to find / consume at the right time. 

Of course Qlik aren't going to change the fundamental way search works but we wondered if some enhancement to the search experience might help... let's call it "Search Assistance". By default, things would work as they do now, but as part of the interface (perhaps under the three-dots button) there would be an option to enable different search options like full text and fuzzy. This could then simply change the search term for the user.

e.g.

  • search for roo and you'll see "rooster" (i.e. those values with roo at the start of a word)
  • click the full text option and it will change your search term to *roo* and return "kangaroo", "brood" and "rooster" etc. (i.e. those values with roo anywhere in the string)
  • click the fuzzy text option and it will change your search term to ~roo and return the above plus "bro", "road" etc
Qlik Partner Ambassador 2024
3 Comments
mikaelsc
Specialist
Specialist

this should be the standard search in filter panes: 


@AlexOmetis wrote:
  • click the full text option and it will change your search term to *roo* and return "kangaroo", "brood" and "rooster" etc. (i.e. those values with roo anywhere in the string)

in the current settings, we're forced to write *searchstring* (between stars) to ensure all search values are selected. the problem especially arises when searching combinations of codes and labels (for example medical diagnoses/ICD10 where the code and the label are not separated by a space: for ex I60.6|Subarachnoid haemorrhage from other intracranial arteries) 

Meghann_MacDonald

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.

Ideation
Explorer II
Explorer II
 
Status changed to: Closed - Archived