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...
Forum Discussion
Ok an example. If a name is John W Smith and the user types in John Smith, there are no results.
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.
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.