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

[Fen2]

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

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

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

[Ct111]

Defining a search source is still an option in AI .

Check this LINK

to understand what I am saying.

I would insist you to try this, 

like create another knowledge search source for your AI and then attach it to AI

only change the line which is explained in the solution that is attached by you in question and then see if it works.

Because I don't see that servicenow has released any docs for configuring those settings specifically in AI.

If after doing this it doesnt work then I would insist you to check with HI support team and verify if any setting can be done or not.

[Fen2]

Hello Creativethinker,

Actually a search source is defined, but the issue is the filter on the search source which is by field, like here by default

So basically it seems not possible to do a query like ' * ' + loy, it is working fine with the knowledge as i got results with 3 letters, but not with catalog item

[kamal_s · Accepted solution]

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

[Fen2]

Hello kamal_snow,

ow yes it is working with " loy* ", well as a workaround it can be like that but it seems so weird

Thank you for the answer