
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2019 11:17 AM
Hi all,
Odd thing going on...so I was working on some catalog item development work and I went to our Service Portal in Dev and tried to find the item (that already existed -- I had just added a variable and wanted to see how it looked on SP) and noticed that when I went to search for it....nothing was suggested via typeahead nor when pressing enter...the search results said nothing found. If I search for KB articles, those show up...
So I went to my Test environment...same thing...
So I went to my Prod environment and it works there...
So basically after some comparing, all search sources, widgets, code, etc. all look the same, but my Dev and Test instances were recently patched to Kingston 12. Our Production instance is still Kingston 9. I thinking something may have broken the search functionality on the portal due to the patch. Back-end searching still works for catalog items.
Anyone else on Kingston 12 and can test this for me to see if you see the same issues? I've reached out on our Slack community as well and haven't gotten a response just yet.
I don't see anything on the Known Issues/Errors section in HI.
Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
Solved! Go to Solution.
- 3,926 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2019 12:35 PM
Found the workaround for those not on London:
https://hi.service-now.com/kb_view.do?sys_kb_id=e83a702bdbb12380f0612183ca961941
Essentially:
You can resolve the issue by editing line 16 of the Data Fetch Script to pass in the catalog value which is set earlier in the script, from:
if (!catalog_item.canViewOnSearch() || !catalog_item.getFirstAccessibleCategoryForSearch()) {
To:
if (!catalog_item.canViewOnSearch() || !catalog_item.getFirstAccessibleCategoryForSearch(portalValue)) {
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2019 12:35 PM
Found the workaround for those not on London:
https://hi.service-now.com/kb_view.do?sys_kb_id=e83a702bdbb12380f0612183ca961941
Essentially:
You can resolve the issue by editing line 16 of the Data Fetch Script to pass in the catalog value which is set earlier in the script, from:
if (!catalog_item.canViewOnSearch() || !catalog_item.getFirstAccessibleCategoryForSearch()) {
To:
if (!catalog_item.canViewOnSearch() || !catalog_item.getFirstAccessibleCategoryForSearch(portalValue)) {
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2019 01:48 PM
Nice find, we have been getting reports this week of the same issue. This has resolved it in our test instance, so I will be promoting to production.
Thanks
-Chris

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2019 01:51 PM
Glad the information was able to help you. We've seen no issues with the fix, so hopefully that remains the same for you.
Take care!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2019 09:31 AM
Hi Allen,
But this modification isn't working for me. Still type-ahead search didn't bring up proper results as expected.