Quick Order Component not searching correctly

[lesliekirk]

I swear when I first played with the Quick Order Component I just had to enter the first few numbers of a product code and the field would make suggestions. If I enter say just the first 3 numbers, it shows Product Not Found. IF I enter the entire product code it will find it (if it is correct). I have tried both Runtime and Code Search Methods (from the Advanced settings). What did I forget to do? The docs don't indicate anything that should be checked if it doesn't work.

[SteveoSoule]

When the Quick Order's "Advanced > Search Method" setting is set to "Runtime" it will perform a runtime search according to the "User Interface > Global Settings > Searchable Fields" settings; just like if you were to search in the global-header's search-input.

When the Quick Order's "Advanced > Search Method" setting is set to "Code", it will perform a search where value typed in the search-box has to equal a product-code in the store.

Can you double-check your component's settings with the behavior described above, and let me know if you're seeing something different? I'll also work on getting this clarification added to the documentation.

[lesliekirk]

Yup, as I said, I have tried both ways. Neither is working as expected. I have set this up in a number of stores already so this one has stumped me. Go here. Type 3200 - you should be offered at least two items 32001 and 32007. You have to enter the exact code.

[Nick]

lesliekirk When the quick order is set to use "Code" you need to enter the exact code for it to work, it does not search for the code or do an auto complete.

When I enter 32001 I get a result in the link you have in the post so I am guessing it is set to use "code" and not "runtime search".

[lesliekirk]

lesliekirk When the quick order is set to use "Code" you need to enter the exact code for it to work, it does not search for the code or do an auto complete.

When I enter 32001 I get a result in the link you have in the post so I am guessing it is set to use "code" and not "runtime search".

My apologizes. As I said, I have been trying to get it to work with both settings and have been going back and forth with them. Yes, I had it still set to code. It is now back at "Runtime". Please see if it works for you. It still does not work as expected for me. I've got it working great on other sites and ReadyTheme templates. This one just isn't cooperating.

[lesliekirk]

When the Quick Order's "Advanced > Search Method" setting is set to "Runtime" it will perform a runtime search according to the "User Interface > Global Settings > Searchable Fields" settings; just like if you were to search in the global-header's search-input.

When the Quick Order's "Advanced > Search Method" setting is set to "Code", it will perform a search where value typed in the search-box has to equal a product-code in the store.

Can you double-check your component's settings with the behavior described above, and let me know if you're seeing something different? I'll also work on getting this clarification added to the documentation.

Hey Steve, sorry for the delay. You are correct, I had left it in code "assuming made that would trigger it". I had been going back and forth with both settings because as I mentioned, neither one would work correctly. I have set it back to "Runtime". Please see if it works for you. I've already had the store owner test it when it was in "Runtime" - she was the one that pointed out the issue. Thanks!

[Nick]

lesliekirk Check the Searchable Fields settings. The Searchable Fields settings is what controls how the runtime search works.

My guess is that you have the Product Code set to Full Text, which means the result will only show if the full text matches the query string. If the product code search type is set to Full Text try switching it to Contains (Term)

[lesliekirk]

lesliekirk Check the Searchable Fields settings. The Searchable Fields settings is what controls how the runtime search works.

My guess is that you have the Product Code set to Full Text, which means the result will only show if the full text matches the query string. If the product code search type is set to Full Text try switching it to Contains (Term)

Your guess was correct! Very odd, but it also explains why the default search was not working correctly. It used to be predictive but I noticed it wasn't anymore either. So we have fixed two birds. Many thanks.