How to search only when I press enter?

  • 0
  • 1
  • Question
  • Updated 9 months ago
  • Acknowledged
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?
Photo of Lane Pemberton

Lane Pemberton

  • 292 Points 250 badge 2x thumb

Posted 11 months ago

  • 0
  • 1
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,044 Points 20k badge 2x thumb
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!
Photo of Lane Pemberton

Lane Pemberton

  • 292 Points 250 badge 2x thumb
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.
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 65,280 Points 50k badge 2x thumb
I have never experienced Quick Base erasing key strokes while typing in the filter box.  That sounds like a bug which should be reported.
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,044 Points 20k badge 2x thumb
I was intentionally being ridiculous but not slighting your inquiry. The problem is that QuickBase hard-codes every feature and provides very few ways to customize the product's behavior using script. Your inquiry certainly arises out of a legitimate user's requirement and the whole idea of submitting a suggestion to User Voice and crossing your fingers it will get implemented is fraught with problems.

What you want to achieve can probably be done with script in a couple of lines of code. It is probably just a matter of holding off the default event handling until an carriage return is entered. Can you provide a screentshot of exactly where this search box is located?
Photo of Lane Pemberton

Lane Pemberton

  • 292 Points 250 badge 2x thumb
@Dan - Sorry Dan, I misunderstood your comment. I agree, QuickBase could be made more flexible. 

Attached is the report we're searching.
Photo of Evan Martinez

Evan Martinez, Community Manager

  • 11,406 Points 10k badge 2x thumb
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. 
Photo of Lane Pemberton

Lane Pemberton

  • 292 Points 250 badge 2x thumb
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. 
Photo of Ⲇanom the ultimate (Dan Diebolt)

Ⲇanom the ultimate (Dan Diebolt), Champion

  • 30,044 Points 20k badge 2x thumb
I added a demo of the "search only on enter" to this application:

Chromeless GridEdit ~ Table Dashboard Search on Enter Only
https://haversineconsulting.quickbase.com/db/bnq3damiq?a=td

Pastie Database (Updated)
https://haversineconsulting.quickbase.com/db/bgcwm2m4g?a=dr&rid=658

The updated code is in the section:
if (/a=td/i.test(querystring)) {
  //
}
Photo of Lane Pemberton

Lane Pemberton

  • 292 Points 250 badge 2x thumb
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!
Photo of Jonathan

Jonathan

  • 100 Points 100 badge 2x thumb
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.
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 63,962 Points 50k badge 2x thumb
An alternative is to use an <ask the user> report.