- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 08:33 AM
When I search for the keyword 'I170911_009', it comes out empty.
When I search for the same value in the column directly, it returns a record (as expected).
So how do I modify the keywords to search through the vendor_ticket column? I need this for when searching in the global search.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-08-2018 07:41 AM
I found it. It seems I needed to click 'Generate Text Index' on the collection dictionary for the table. When I navigate to the table record, the indexes were there, and the check box 'Text index' was set correctly, but despite all that, ServiceNow did not generate the text indexes when I moved the table in between environments... After generating the text index, the search shows the expected results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 09:24 AM
If you search in the global text search for this same term, does it fail or provide a response?
Can you also check the table - yourinstance.service-now.com/text_search_list.do and see if the term is in the search_term and tokenized_term listing?
If so, which table(s) does it return?
Finally, can you check yourinstance.service-now.com/ts_stop_list.do and see if the search term 'I170911_009' is a stop word?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 11:17 AM
text_search_list.do seems to point me in the correct direction.
On our dev instance, I have 24 results, while on our prod instance I have only 23 results, with the specific table missing.
I checked the 'text search group', that I had created for my newly defined table, and everything seems to have moved to production just fine. Both the text search group and linked text search tables are defined the same as on our dev environment. Though, the results are not coming in.
It's late, so I'll continue tomorrow. But I guess, what I need to figure out is, why the search group is not kicking in on our prod environment. There is a role restriction on the search group, but I'm admin (and have the specified role), so I tried to log in again, but that did not work either. Emptying the cache did not work either.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 09:31 AM
Hello Peter
In your first scenario it is searching the word as Keyword = 'I170911_009', but in case of column search it is vendor ticket starts with 'I170911_009'. I think you have to apply the filter right and you should be good.
Please mark my response as correct and helpful if it helped solved your question.
-Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2018 10:01 AM