SharePoint Search: full-text queries matching fragments of UniqueId / ListId document properties

Paolo De Paulis 1 Reputation point
2022-07-21T09:46:29.093+00:00

We found out the hard way that, by default (as this behavior is reproducible on SP2019 vanilla farm installations), SharePoint Search includes a tokenized version of documents' UniqueId/ListId into its full-text index. A screenshot will explain the situation better than a thousand words:

223073-screenshot-2022-07-21-113947.jpg

We found no way to configure this behavior, as UniqueId/NormUniqueId/ListId/NormListId managed properties aren't searchable, and ows_UniqueId and ows_ListId crawled properties aren't included in the full-text index, so "Search Schema"-wise they shouldn't already be there.

Is there some way to exclude those properties from the index? We have some custom metadata that must be searchable and is similar to the guid parts being matched, so this is causing a lot of irrelevant results to be returned to users.

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,421 questions
SharePoint Development
SharePoint Development
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Development: The process of researching, productizing, and refining new or existing technologies.
3,290 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.