Forum Discussion

JimHarrison's avatar
JimHarrison
Qrew Champion
7 years ago

Browse Choices Search Feature

We have a large table for Contacts. When on forms we want to select a Contact from the table. There are too many choices and the Browse Choices feature appears. When we search the Choices if the entry is not exact, the search returns nothing.

The Browse Choices feature should return anything that contains the search text, this way users can filter through the results instead of constantly getting no results until the correct search text is hit upon. 

What do you think?

I created this if you agree vote on it. 
https://quickbase.uservoice.com/forums/111823-quick-base-product-feedback/suggestions/33803092-brows...
  • QuickBaseCoachD's avatar
    QuickBaseCoachD
    Qrew Captain
    7 years ago
    I think that your User Voice is premature.  The pop up record Picker Browse function is definitely a contains search.  If you did a trivial search on an "a" without the quotes)  for example you would get tons of hits.

    Are you perhaps searching on two words or partial words and not getting hits?  That would be a different issue as the contains search will be looking for that phrase contained in the text.

    Also note that the initial search is done against the fields showing in that pop up box.  If these are set to be just the default record picker fields, you may want to specify a report in the form to use, so that more fields will be initially searched.
  • JimHarrison's avatar
    JimHarrison
    Qrew Champion
    7 years ago
    That's what I get. You are correct, I will have to do more research on why another user is having this issue. Garrrr! 

    Deleted
  • JimHarrison's avatar
    JimHarrison
    Qrew Champion
    7 years ago
    Ok an example. If a name is John W Smith and the user types in John Smith, there are no results.
    • QuickBaseCoachD's avatar
      QuickBaseCoachD
      Qrew Captain
      7 years ago
      OK, now I understand.

      My comment is to you and Sam.  Google pretty much  owns "search" so Google behaviour is what users expect.

      So it would better to have Browse searches and the filter box on the top of reports and contains search on <ask the user> reports follow google type logic so that  a two word search would not be treated as a phrase,  but rather a double contains search like 

      like contains 

      john AND smith 

      I'm sure that the complicated part for Quick Base is anticipating the negative fallout from a change to the search behaviour.  Who knows what legacy apps would get broken by such a change.

      Maybe it would be an App Level and Realm level setting and then New Realm Accounts would be defaulted to the Google behaviour for Contains searches and old accounts could opt in.