Order Guide wrong view in the portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 12:10 AM
Hello
I am trying to configure the AI search so that when it is an order guide, it redirects to the correct page. Someone who can help me, I have seen other previous questions in the forum, but it is not the solution I am looking for...
Help me!
How is currently configured.
What I do expect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2023 12:15 PM
I have the same issue

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2023 10:19 PM
Not sure if you're still experiencing this, but just in case someone else comes across this I found a solution. In my case, it was the genius results that were not directing the user to the correct view of an order guide. While the AI Search Results Action Configurations has a record called 'Genius Navigation Catalog Order Guide', it wasn't configured for the AI Search Source that was being used. To resolve the issue, I had to create a new record based on the 'Genius Navigation Catalog Order Guide' record, but change the AI Search Source to the one being used by my portal (in my case it was [AI Search Assist] - Service Portal Catalog). Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2024 06:13 AM - edited 06-12-2024 06:39 AM
Hi all,
I think this is a ServiceNow issue related with the EVAM View Configs custom conditions / column mappings.
I was able to fix this with little customisation (after a lot of testing).
You can follow these steps to get to the key configurations.
1- Go to your Portal and access it Search Result Configuration:
2- Open the EVAM Vew Config Bundle where "Taxonomy - Catalog Order Guide Genius Results" should be located.
3- Open "Taxonomy - Catalog Order Guide Genius Results"
4- At this point we shoud be seeing this:
I do not know why, but the value of "record_class_name" column in this case will allways be "sc_cat_item", so this OOB configuration will never work. I suppose ServiceNow has mapped that column with Cat Item Table column instead of Class column. I could not reach that mapping configuration.
To fix this issue I have created a Dynamic Filter so I can place it in the Custom Conditions, filtering by the column Sys ID.
5- Create a new Script Include (client callable), this is my example:
Name: orderGuidesIDs
Script:
function orderGuidesIDs() {
var ids = [];
var grOrderGuides = new GlideRecord("sc_cat_item_guide");
grOrderGuides.query();
while(grOrderGuides.next()){
ids.push(grOrderGuides.getUniqueValue());
}
return ids;
}
I made it available for All aplication scopes, but it may not be necessary.
Inserted and adjusted the role permissions.
6- Create a new Dynamic Filter, calling the previous script:
7- Go back to "Taxonomy - Catalog Order Guide Genius Results" and change the Custom Condition:
In my case:
columns.var__m_sys_search_genius_result_field_095e15b9c32310109e777d127840dd59.__sys_idDYNAMIC98fd1db0873a42505c74eca83cbb35fd
- 98fd1db0873a42505c74eca83cbb35fd is the ID of my dynamic filter, copy yours and palce it afer "DYNAMIC"
- __sys_id is the internal name of the column sys_id.
8- Save and test it in your Portal.
If it does not work consistently, go to "Search Results Actions" Module and search for "Genius Navigation Catalog Order Guide", for the AI Search Source your portal is using.
Make sure it has less Order than "Request Item" action configuration:

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2025 01:52 PM - edited 03-25-2025 01:53 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!