AI Search Index Source & Search Source Configuration for Task table

Brent Sutton
Mega Sage

‎03-07-2023 02:17 PM - edited ‎03-07-2023 03:05 PM

I'm hoping this is a simple one to answer.

 

I'm trying to create an AI search indexed source and search source that will allow users to search for their active tasks via Employee Center portal.

 

Steps taken:

  1. Index Source - I've created an AI Search Index Source for the task table and restricted indexing to active "Change Request" and "Requested Item" task types (will be adding more later).
  2. Child Tables - Added the extended CHG [change_request] & RITM [sc_req_item] tables as child tables for the index source.
  3. Indexed all the tables.
  4. BrentSutton_3-1678226399439.png
  5. Search Source - Created a Search Source mapping with a condition to restrict users search results to ones they raised. The RITM "requested_for" and CHG "requested_by" fields are on the child tables linked to the indexed source. Encoded query below:

 

 

 

 

 

active=true^sys_class_name=sc_req_item^ref_sc_req_item.requested_forDYNAMIC90d1921e5f510100a9ad2572f2b477fe^ORopened_byDYNAMIC90d1921e5f510100a9ad2572f2b477fe^NQactive=true^sys_class_name=change_request^ref_change_request.requested_byDYNAMIC90d1921e5f510100a9ad2572f2b477fe^ORopened_byDYNAMIC90d1921e5f510100a9ad2572f2b477fe​

 

 

 

 

 

  1. Upon save of the search source I get an error "Search Source condition could not be saved. See logs for details." and "Invalid Insert" (see screenshot).
  2. BrentSutton_1-1678226213412.png
  3. When I look at the logs, I see an error message "dot-walk column doesn't exist task.ref_sc_req_item.requested_for" for RITM and "dot-walk column doesn't exist task.ref_change_request.requested_by" for CHG.
  4. BrentSutton_2-1678226293394.png
  5. I believe that a field setting may need to be created on the Indexed Source. However, there doesn't appear to be the option to use the dot-walk attribute for the task table or the ability to select child tables for the field selection.
  6. BrentSutton_0-1678226106541.png

     

I've looked at numereous support articles and ServiceNow docs trying to resolve this issue. I'm sure I'm not the first person to attempt indexing the Task table while restricting results using fields on child tables. Any guidance on how to achieve this, or suggestions for an alternative approach with a similar outcome, would be much appreciated.

Labels:
0 Helpfuls
  • 2,694 Views
11 REPLIES 11

Brent Sutton
Mega Sage
In response to Brian Bakker

‎06-16-2025 02:00 PM

@Brian Bakker - Yeah, I'm pretty sure what you are describing is the route we had to take (been a while since I was looking at this).

 

In our case, the customer only wanted a single 'Task' source, so their users had incidents, changes etc displayed in the same search results tab. Seems like a reasonable assumption that this should be possible to configure but it wasn't the case. Dot-walking to specific fields, only found on child tables, prevented this from working.

0 Helpfuls

jokin
Tera Expert
In response to Brent Sutton

‎07-09-2025 01:10 AM

I got it confirmed from Servicenow that it's not still possible to use child table fields in filters ( Yokohama release). So we went for one tab per indexed source .

 

"I have been reviewing the issue where you are unable to dot walk to child table fields in the Task Heirarchy while configuring the filters in your child source."

…..

"However, this functionality is not currently available for child tables within the task hierarchy."