We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Not able to set dynamic filter to search source record of ai search

anuj27
Tera Expert

I have configured a new indexed source as incidents for AI search on portal.

It did setup but it was showing incidents which were not mine. So I decided to add filter that incidents it shows must belong to logged in user.

 

So to achieve this , What I have tried is to add the filter to search source record and limit that to current logged in user records.

Requested For is(dynamic) Me  (Refer screenshot),

// Search source record filter

anuj27_3-1721596592521.png

 

But as soon as I save the record. Few error pops up and says invalid update. See Screenshot

anuj27_4-1721596592595.png

 

---

Upon searching the internet, I found that it is becz the reference field I used in search source filter( Requested For ---- backend name : caller_id) is not configured via dot_walk_fields attribute in related list' field mapping and setting' in index source record. 

 

So I decided to add that, See screenshot

anuj27_5-1721596592598.png

 

---

After doing all this Still I am not able to apply that filter on search source record and it is still giving me same error.

What I am missing here, Can you help me with this ??

 

Thanks

3 REPLIES 3

Bhavya11
Kilo Patron

Hi @anuj27 

 

For more information refer below links

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1117071 

https://www.servicenow.com/community/intelligence-ml-forum/ai-search-index-source-amp-search-source-... 

 

Please mark helpful & correct answer if it's really worthy for you.

 

Thanks,

BK

If this information proves useful, kindly mark it as helpful or accepted solution.

Thanks,
BK

Hi @Bhavya11 , but the KB article says that it got fixed in "San Diego Patch 4". 

Also Official doc of search sources says that dynamic filter can be applied.

anuj27_0-1721735486110.png

Jose Manuel
Tera Contributor

Could you solve this issue?

 

I was thinking about hardcoding the conditions (via script and putting setWorkflow(false)) or inactivating the Business rule that aborts the save action.