Answers.Body: <p>Try your search using % as a wildcard - like %lorem%</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T18:12:50.383Z
Answers.Text: Be careful with % wildcards - see Eileen's https://civicrm.org/blog/eileen/would-you-like-coffee-while-you-wait-sir
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T18:46:04.583Z
Answers.Text: KarinG, a good point, and Eileen's blog post is definitely worth reading, and the variations for using % in a search worth looking at. But a 'slow' search using %, with a desired result, is better than a fast search which returns no result, right?
Answers.UserDisplayName: Joe McLaughlin
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-16T16:02:43.297Z
Answers.Text: %lorem% also showed no results.
Answers.UserDisplayName: 406CODE
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-16T16:08:02.407Z
Answers.Text: For this particular project, it's all about the search. Our users need to be able to find previous cases or clients. For example, cases about irrigation in Nebraska, or sheep grazing in Montana. They need to be able to search clients who are veteran farmers in Virginia. In this particular case, a slower search with desired result is not only preferred, it's a requirement. Users today are also used to Google and other search engines. They are accustomed to entering "sheep gra" and getting hits for "sheep grazing", "gray sheep", or "sheep in the grand valley". This is what they want.
Answers.UserDisplayName: 406CODE
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-13T18:08:19.703Z
Answers.LastActivityDate: 2016-05-13T18:08:19.703Z
Answers.UserDisplayName: Joe McLaughlin
Body: <p>First, I'll explain how I stumbled upon the issue. We need some serious, working search functionality.</p>
  
  <p>I set up a custom field for cases. I set up the custom field to be searchable.</p>
  
  <p>I then created a test case and populated my new field with latin text "Lorem....".</p>
  
  <p>I then tried to find my new case with case search and "lorem" in my custom field. It couldn't find it.</p>
  
  <p>I then tried to find the new case with the new field using "full-text search". It couldn't find it again. I then started testing full-text search. It seems to be hit and miss.</p>
  
  <p>Perhaps it's user error, and in that case, please advise what I'm doing wrong. I would appreciate it.</p>
  
  <p>For the following tests, I'm using "all tables" and yes, I have wildcards enabled.
  Full-text search doesn't find "lorem" which is in my case custom field. Full-text search doesn't find "john" which is in the name of several contacts (john, johnson...). 
  Full-text search doesn't find "j" which is in many fields in many tables.
  Full-text search only finds four hits for "a" which are all names of contacts.
  Full-text search doesn't find "max" which is in at least four contact's names.
  Full-text search does find three hits for "bob" all within contact's names.
  Full-text search does find two hits for "sheep" which are all in case descriptions.</p>
  
  <p>Can anyone shed some light on these inconsistent results?</p>
  
  <p>Thanks so much!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-13T18:11:12.670Z
Comments.Text: What version of Civi are you using? Would be helpful to update your question with that.
Comments.UserDisplayName: Joe McLaughlin
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-05-16T16:00:55.203Z
Comments.Text: We are using version 4.7.6 .
Comments.UserDisplayName: 406CODE
Tags: <search><search-results>
Title: full-text search not working consistently; case search in custom field not working
ThreadText: # full-text search not working consistently; case search in custom field not working
  
  (Asked by: username_0 on 2016-05-13)
  
  First, I'll explain how I stumbled upon the issue. We need some serious, working search functionality.
  
  I set up a custom field for cases. I set up the custom field to be searchable.
  
  I then created a test case and populated my new field with latin text "Lorem....".
  
  I then tried to find my new case with case search and "lorem" in my custom field. It couldn't find it.
  
  I then tried to find the new case with the new field using "full-text search". It couldn't find it again. I then started testing full-text search. It seems to be hit and miss.
  
  Perhaps it's user error, and in that case, please advise what I'm doing wrong. I would appreciate it.
  
  For the following tests, I'm using "all tables" and yes, I have wildcards enabled.
  Full-text search doesn't find "lorem" which is in my case custom field. Full-text search doesn't find "john" which is in the name of several contacts (john, johnson...).
  Full-text search doesn't find "j" which is in many fields in many tables.
  Full-text search only finds four hits for "a" which are all names of contacts.
  Full-text search doesn't find "max" which is in at least four contact's names.
  Full-text search does find three hits for "bob" all within contact's names.
  Full-text search does find two hits for "sheep" which are all in case descriptions.
  
  Can anyone shed some light on these inconsistent results?
  
  Thanks so much!
  
  **Tags:** search, search-results
  
  > **Comments:**
  > **username_1**: What version of Civi are you using? Would be helpful to update your question with that.  
  > **username_0**: We are using version 4.7.6 .  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-05-13. Score: 0
  
  Try your search using % as a wildcard - like %lorem%
  
  > **Comments:**
  > **username_2**: Be careful with % wildcards - see Eileen's https://civicrm.org/blog/eileen/would-you-like-coffee-while-you-wait-sir  
  > **username_1**: KarinG, a good point, and Eileen's blog post is definitely worth reading, and the variations for using % in a search worth looking at. But a 'slow' search using %, with a desired result, is better than a fast search which returns no result, right?  
  > **username_0**: %lorem% also showed no results.  
  > **username_0**: For this particular project, it's all about the search. Our users need to be able to find previous cases or clients. For example, cases about irrigation in Nebraska, or sheep grazing in Montana. They need to be able to search clients who are veteran farmers in Virginia. In this particular case, a slower search with desired result is not only preferred, it's a requirement. Users today are also used to Google and other search engines. They are accustomed to entering "sheep gra" and getting hits for "sheep grazing", "gray sheep", or "sheep in the grand valley". This is what they want.  
  
  ---
  
  