Property to know where search query has got the match in SharePoint search search API

Sachin Jindal 0 Reputation points

I am using REST service search api on a library and I want to know where the keyword is matched it is in the document or any column.

I am new to the platform do let me know if any more information is required.

Thanks in advance.

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
9,935 questions
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
9,151 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.
2,547 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ChengFeng - MSFT 4,995 Reputation points Microsoft Vendor

    Hi @Sachin Jindal

    This query is against the entire SharePoint environment and by default it will search for anything that contains the specified keyword. It is not limited to a specific column, but performs a full-text search across SharePoint

    When you provide a keyword as a parameter, SharePoint looks for matches containing that keyword in all searchable content, such as documents, list items, web pages, and so on. Search results will contain querytext

    If you want to search against a specific column, you can use SharePoint's search query syntax to scope your search. For example, using property:value

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best Regards

    Cheng Feng

    0 comments No comments