Forum Discussion

AustinHayes's avatar
AustinHayes
Qrew Cadet
7 years ago

How to utilize multiple ask the user filters in single query while allowing for situations with no input for some of the filters.

I am looking to utilize multiple ask the user contains queries with an all condition. I run into problems when the user leaves any of the ask the user filters blank; no results are pulled back because no records are found containing '' for whichever field(s) are left blank. I need to maintain the all filter condition while allowing for blank inputs in any of the fields.
  • I seem to recall that I use this technique in the past.

    I created a mirror Field for example a field called [customer name or enter * for all]

    With the formula

    [customer name] & "*"

    So the result is ACME INC.*

    Then I use that field for the Ask then User prompt and try to train the users to know that they put in an * for a wildcard.

    But this tactic will only work for a contains search
    • AustinHayes's avatar
      AustinHayes
      Qrew Cadet
      I am utilizing this tactic right now. It works well enough, I appreciate the input. It isn't perfect but certainly gets the job done. Is there a way to set the fields to * by default on load?
    • AustinHayes's avatar
      AustinHayes
      Qrew Cadet
      How do I mark this answered? I am  satisfied with the implementation of you original solution.
    • QuickBaseCoachD's avatar
      QuickBaseCoachD
      Qrew Captain
      You can do a "Like" if you want to ping me, but this new forum no longer has the concept of "Answered".
  • Thanks, I appreciate the option. It seems quickbase has not really designed for an elegant solution to this?
  • I'm sure we can come up with something. Can you post more information about the exact workflow your user follows? My first thought would be something along the lines of creating helper fields for each filterable field, where the helper fields are formula fields, and the filter is done on the helper field rather than the data entry field. Sort of the reverse of Coach's suggestion, in a way.

    I don't know if you'd call that kind of a solution ELEGANT, exactly...