I have created a search form with a single input, the query runs find, but always returns all results, the ask later never seems to connect.

Could not figure out what I is wrong with this, so I looked at the CRM app. Seems the search in the banner is not working either, although the results I get on that one are really odd and might not be related.

Am I doing something wrong, is this a defect, both?

<input type="text" name="Goals" id="Goals" size="20" title="Enter Goal Name, Owner, or Record ID">

<input type="button" onclick="var params = {}; params ['Parameter'] = document.getElementById ('Goals').value; AwareApp.runQueryWithParams('Fast_Find_Goals', params, 'new_tab'); return false;" value="Go" name="B1" title="Click to start search">

Also the find in library app seems to have the same behavior as CRM.

Seems to work fine for us. How do you reproduce the problem in the CRM app?

log in to the live smaple of CRM app as staff member - from the find by customer the name search in the banner frame, hit search with no value, you should get a 2 page list. Find Rosemary Flint on the list.

repeat search for Flint - I get no results

repeat search for Rosemary - I get no results

repeat search for F - I get 3 results but not rosemary flint

According to the Query definition this should be doing a contains on customer.firstname and customer.lastname. I do not know what it is running, but but it is not that...

Same for library app, search for Harry. The first HP book is on the list, but is not in the results.

Ok, I figured it out. The sample query parameters are case sensitive...

also figured out my issue, YAY!

I had to change the query using the Rule Form from

FIND Goals WHERE Goals.Summary CONTAINS ?Summary AND Goals.Inactive<>'Yes'

To

FIND Goals WHERE Goals.Summary CONTAINS ?Parameter AND Goals.Inactive<>'Yes'

The way I found this was by looking at the Rule Form SQL of the CRM Sample Query 'Correspondence using single parameter', but ft you compare the simple form view to the query I had, then it looked exactly the same. In hind sight this seems logical, but was not intuitive for me to stumble upon so I was thinking this might be worth noting in the documentation (unless I missed it!!).