- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2022 02:23 PM
Hi Community,
Just wondering if anyone could provide some suggestions or thoughts on this problem. We've recently upgraded to Tokyo and our portal search experience got a nice little upgrade. We now have "Suggestions" which provides us with a quick way to open items during a search.
Unfortunately, we've run into an issue where our order guides are being opened as an sc_cat_item, instead of sc_cat_item_guide when the user uses the "Suggested" feature. As such, the order guide isn't presented properly (does not have the "Next" button or the "Choose Options" button to proceed us to the next step). However, if the user completes the search to see the full results and then selects the item, they will be able to access the result properly (as a sc_cat_item_guide).
As an example:
If the user clicks the "Suggested - Order Guide - TEST", they will be brought to the order guide with the following URL:
https://<instance>.service-now.com/sp?id=sc_cat_item&table=sc_cat_item&sys_id=<sys id>
Whereas if they were to see the full list of results from the search and then click on the item, they would be brought to the order guide with the following URL:
https://<instance>.service-now.com/sp?id=sc_cat_item_guide&table=sc_cat_item&sys_id=<sys id>
We've tried:
- Marking the order guide as "No Search" - but this prevents the item from being searched at all
- Adjusting the Search Profile/Search Source (AI Search > Search Experience > Search Profiles) to hide the Class of Order Guides from the search results - the order guide as a Catalog Item shows up
- Trying to add order guides as a Facet in the Search Applications (AI Search > Search Experience > Search Applications) - but we get an error "Invalid table name: "sc_req_item_guide". Please ensure that the table is defined in the current search profile's search sources."
- So we tried to add an indexed source for the sc_cat_item_guide table but it doesn't exist
- So we tried to add an indexed source for the sc_cat_item_guide table but it doesn't exist
At this point, it looks like we are either going to have to disable the Suggested results from showing up or deal with the backlash of our end users being unable to submit an order guide. Our intention would be to be able to prevent specific items (our order guides) from appearing as a Suggested item in the search experience.
Any tips or suggestions would be really appreciated!
Thank you
Solved! Go to Solution.
- 9,668 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2023 04:05 PM
Hi Dale,
Try this:
function onLoad() {
//Type appropriate comment here, and begin script below
var qury = getParameterValue("id");
var sysId =getParameterValue("sys_id");
//alert('ji-- '+qury);
if(qury == "sc_cat_item"){
top.window.location = "/sp?id=sc_cat_item_guide&table=sc_cat_item&sys_id="+sysId
}
function getParameterValue(name) {
name = name.replace(/[\[]/, "\\\[").replace(/[\]]/, "\\\]");
var regexS = "[\\?&]" + name + "=([^&#]*)";
var regex = new RegExp(regexS);
var results = regex.exec(top.location);
if (results == null) {
return "";
} else {
return unescape(results[1]);
}
}
}
Created on the order guide as an onLoad script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2024 08:48 AM
Hi,
I am having exact same issue in our client's instance. I was wondering if there's anything else besides the script mentioned as part of the solution that I can look into to resolve the issue. Please let me know.
We are having this issue in UAT environment only.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2025 01:54 PM
In case anyone else finds this post because they have the same issue, ServiceNow has posted a workaround in KB1949808, namely, either patch to Xanadu Patch 7 or Yokohama Patch 1, or apply a workaround, which is to create a new system property [sys_properties] record named 'glide.search.evam.use_legacy_template_generation', Type true | false, and set it to 'true'. Once you're patched to a version noted therein, this system property should be removed.
Ref: KB1949808
Please mark this response as the answer if it helps you. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-20-2025 06:47 AM
I had to add this, even tough I'm on Xanadu Patch 8! Wonder if anyone from ServiceNow will see this.
Thanks for the tip. 🙂