Loading...
Loading...
After upgrading to Australia Patch 6 , Brazil Patch 0, or Brazil Patch 1 , AI Search search sources that filter on a Table Name or Field Name type column no longer match records that were indexed before the upgrade. These release versions changed how Field Name and Table Name column types are indexed, and existing records are not automatically re-indexed into the new format on upgrade. A key symptom is that Skill / Topic discovery returns no skills after upgrading to the affected release versions. The Generative AI Skills table, sys_gen_ai_skill, has a column called "Skill Table" of type Table Name in sys_dictionary. When a search source, such as those used by ServiceNow Otto for Virtual Agent, filters on Skill Table = some value, because of the change to how Table Name type columns are indexed, no results will return for already indexed skills. Skills updated or created after the upgrade will be discoverable because they will have indexed in the new format, while records untouched since the upgrade will remain undiscoverable. Importantly, any Indexed Source with a Search Source filtering on Table Name of Field Name column types is affected similarly.
Scenario 1 — Skill and Topic discovery (most common) 1. On an instance that already has skills indexed, upgrade to Australia Patch 6 , Brazil Patch 0, or Brazil Patch 1 from an earlier release. 2. In a conversational interface such as Virtual Agent, search for a skill that worked before the upgrade (for example, "Book a meeting"). 3. The skill is not found and does not execute. 4. Update the failing skill record or re-index the Skills indexed source. The skill is found and executes as it did before the upgrade. Scenario 2 — any other search source filtered on a Table Name or Field Name column 1. On an instance with content already indexed, upgrade to Australia Patch 6, Brazil Patch 0, or Brazil Patch 1 from an earlier release. 2. Identify a search source whose filter condition references a Table Name or Field Name type column. 3. Run a search that uses that search source. Records indexed before the upgrade are not returned, while records created or updated after the upgrade are returned normally. 4. However, update an affected record, or re-index its indexed source, and now the record is returned as expected. Workaround 1. Re-index the affected indexed source. For Skill and Topic discovery, re-index the Skills indexed source from the AI Search Admin Console, or from All > Indexed Sources. 2. Wait for ingestion to complete. Re-indexing writes the records with the updated format for Table Name and Field Name fields, and results return as expected.
PRB2089496
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.