Forum Discussion

LanePemberton's avatar
LanePemberton
Qrew Cadet
7 years ago

How to search only when I press enter?

I have a few users that search through tables frequently (we filter as much as we can with reports, their varied workflows just require them to do this) and sometimes have a problem typing in keywords. It seems like Quick Base tries to automatically start searching before they're done typing and prematurely returns search results while erasing the latest keystrokes entered. Can I bypass this default setting that automatically starts searching as the user is typing?
  • I mocked up an interface for the benefit of QuickBase's developers that list a few options for controlling this feature:



    Just imagine what the product would look like if every feature under the sun was hardcoded as an checkbox option!
    • LanePemberton's avatar
      LanePemberton
      Qrew Cadet
      @Dan - Sorry Dan, I misunderstood your comment. I agree, QuickBase could be made more flexible. 

      Attached is the report we're searching.
    • LanePemberton's avatar
      LanePemberton
      Qrew Cadet
      I appreciate you going to the effort of creating a mock interface. However, checkboxes wouldn't be used as only one of the options you created would be selected at one time. Therefore, you would only use one row with a dropdown.

      I understand you're trying to highlight how hard it would be to handle every option under the sun, but your options regarding keystrokes and voice command are a little ridiculous. I wasn't trying to say we need every feature in the world. I was trying to start a discussion about an issue our company has consistently dealt with and see if it was an important issue for anyone else. Thank you for your feedback.
    • QuickBaseCoachD's avatar
      QuickBaseCoachD
      Qrew Captain
      I have never experienced Quick Base erasing key strokes while typing in the filter box.  That sounds like a bug which should be reported.
  • Hi Lane,

    Thank you for your feedback on the table search bar and the issues your team is running into when using it with the current set up. There isn't currently an option native to disable that search behavior on a table/report based search so that it doesn't default to searching when it senses that a user has stopped typing. For some heavily used reports and searching a dashboard search widget set to that table or report behaves a bit differently and doesn't search until the user hits enter, which can help with a specific report that you run into this issue regularly with in the short term. 

    I would suggest also submitting your feedback from your experience in our User Voice feedback platform. it is a customer facing feedback forum that our development team use to explore customer suggestions. It is a good place to get visibility for your issue as other users can vote for your issues to show their support giving our Product Development team an idea of how many other users would like to see a change to the search behavior above and beyond our internal feedback. It can be most easily accessed from the My Apps page in Quick Base by clicking on the orange Feedback tab or at http://quickbase.uservoice.com. I would also suggest if you do end up putting your feedback in our User Voice forum that you link it here so that those following this conversation can add their vote. Thank you very much for your time today. 
    • LanePemberton's avatar
      LanePemberton
      Qrew Cadet
      Thanks for your feedback. I might try that after giving Dan's solution a try. My only hesitation with that approach is I don't like to change user's workflows if I can help it. Most of our heavy QB users are used to doing things a certain way and I'd hate to switch that up based on a relatively small aspect of that workflow. _
    • LanePemberton's avatar
      LanePemberton
      Qrew Cadet
      You're crazy. Very impressed with everything you've done to enhance native QB functionality through IOL, ELM, etc. I started going through your database and found some solutions to other features we've been wanting to implement, so thank you!
  • I'm glad I'm not the only person looking for fix for this issue. From a design standpoint I understand that having Quickbase start searching automatically seems like a feature, but given that it also eats our inputs during that split second where it's executing the search, in practice it becomes far more of a bug. As a result every other time I perform a search it takes me multiple attempts to get Quickbase to search for the intended string.