What's the difference between no_text_index and not_searchable? (AI Search)

[Chris D]

I know what the documentation says (Field settings (servicenow.com))...

no_text_index

Option to disable indexing of searchable content from the selected field on records from the indexed source. Supported values: true: Disable searchable content indexing for the selected field. Search and filters can't match the field's value. false: Enable searchable content indexing for the selected field. Search and filters can match the field's value.

not_searchable

Option to disable search matching for content indexed from the selected field. Supported values: true: Disable search matching for content indexed from the selected field. Search can't match the field's value. Filters (such as for content security, navigation tabs, and facets) can still match the field's value. false: Enable search matching for content indexed from the selected field. Search and filters can match the field's value.

But this doesn't seem clear to me - they seem to be doing the same thing... maybe I just can't tell the functional difference between "searchable content" and "search mapping for content" so can anybody clarify in different terms what the differences are between these two field search settings?

[Gerard Dwan · Accepted solution]

'Not Searchable' is for the ability to store and present fields without searches matching against them. It's really an optimization. 

A possible example of something that you would want stored, but wouldn't want searchable is the url for external content. You would want the user to be able to navigate to the url, but searching on it usually isn't important. 

The same is true for fields you may want to use as filter values, but not necessarily search against. 

'No Text Index' is ignored entirely. 

Does that help clarify? 

[Chris D]

Ahh... ok I think the underlying concept is something I didn't realize but can help explain this (correct me if I'm wrong): by default, all the fields of an indexed table are indexed and searchable unless you used one of these properties.

But very helpful, yes thank you!

[Gerard Dwan]

that's right!