Hello Matt,

1. Are you using English as language in both environments for the user that does the search ?

2. Is maybe the word "123456" a stop word? Go to ts_index_stop.list and see if that string is a word there.

Regards,

Thanks Sergiu.

1. We're on the default EN convention on both instances. All our users language profiles are set to this.

2. 123456 was just an example. This is happening for any combination that a user tries. But no, there are no numbers in our stop words list.

As admin, enable "Debug Text Search" , do a text search and paste the output you get here so I can have a look.

See below screenshot as an example:

Regards,

Thanks.

Search results for searching on 356696 on live (returns 0 results)

http://dumptext.com/eA4Ov7Kx

Compared to searching for LUINC0356696 on live (goes straight into the incident, though if i click on 'Exact search match. Click here to see full search results.' this also returns no results)

http://dumptext.com/ivJWDH0v

Compared to searching for 179663 on sandbox (returns 1 result)

http://dumptext.com/02NbXhIW

Hi Matt,

I could only view the first dump output the other two have expired. Anyway, the debug output shows it can't find anything for "356696".

To check:

1. Has your instance been upgraded to Calgary text search? Go to System Definition -> Text Indexes -> Under Related Links -> if upgrade to Calgary Text Search has not been done then there should be a link "Upgrade to Calgary Text Search". If that's the case, you should upgrade the text search engine by clicking on that link. This should be done maybe end of Friday so it has enough time to regenerated all text indexes (it does that) over the weekened.

Regards,