Ai Search can't lookup for the first letters of a catalog item

Go to solution
Fen2
Tera Contributor

‎12-28-2022 06:19 AM

Hello all,

 

As i browsed the community, i didn't find a solution to this,

We enabled ai search and set it up correctly, it works fine,

But we have an issue, where we are in the portal, and want to look for a catalog item with the 3 first characters, ai search doesn't find an item

Fen2_0-1672237109284.png

Or if i put a word, it works fine like below

Fen2_1-1672237141428.png

 

 

As before, we could configure it within a search source (link below), like in this article, i want to do the same request but with ai search, can anyone have an idea on how to do it ?

 

https://www.servicenow.com/community/now-platform-forum/service-portal-search-terms/m-p/1107385

0 Helpfuls
  • 1,264 Views
1 ACCEPTED SOLUTION

Go to solution
kamal_s
ServiceNow Employee
ServiceNow Employee

‎12-28-2022 10:54 PM

Hi Fen2,

AI Search uses a bit more complex way of searching and doesn't rely on exact text matching algorithm similar to Zing. I would suggest instead of making it work similar to Zing, you may try using " * " keyword in your query and educate the users on the available keywords to better use AI.

Query: loy - no result

New Query: loy* - result

View solution in original post

5 REPLIES 5

Go to solution
Gerard Dwan
ServiceNow Employee
ServiceNow Employee
In response to Fen2

‎12-29-2022 07:12 AM - edited ‎12-29-2022 07:13 AM

Thanks @kamal_s , you are correct. Some more background: 

 

This type interaction is best suited for autocomplete. If you are on Tokyo, you can use search-based autocomplete which will evaluate beginning of word matches in the title. 

 

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/ai-search/concept/a... 

 

Generally speaking, allowing for queries like that add noise to search results and often increase latency, so adding wild cards for every query is frowned upon (occasional is ok).