The 'SharePoint Search' data source retrieve items from the SharePoint search engine.
The SharePoint search is different from the Microsoft Graph search.
|Query text||The input query text to pass to the search engine. This setting is not configurable directly in the data source options. To enable it you use go the the third configuration page of the Web Part and selected either a static or dynamic value (Ex: from a connected search box Web Part). See the connection documentation for more information on how to configure this option. This value can be then used in the Query template using the
|Query template||The search query template to use. It allows you to use dynamic tokens according to the context or specifiy conditions that should always apply to the query.||
|Result source ID||Can be either a built-in result source ID listed in the dropdown, or a custom result source that you specify. Type the
|Selected properties||The SharePoint managed properties to retrieve from the results. They can be used with the same name in layouts and slots afterwards.||
|Sort order||The initial results sort order. You will be able to select only 'Sortable' managed properties here. Make sure the selected properties satisfy this criteria in the SharePoint search schema.||None.|
|Refinement filters||The initial refinement filters to apply to the query. Both KQL (Keyword Query Language) and FQL (Fast Query Language) expressions work here (Ex: KQL
|Language of the search request||The language to use for the search request. By default the search request will be made using the current user interface language. This parameter is mainly use to process diacritics, plurals, etc. correctly according to the language.||Current UI language.|
|Enable query rules||Whether or not apply SharePoint query rules.||False.|
|Include OneDrive for Business results||Whether or not include OneDrive for business results.||False.|
|Enable audience targeting||Whether or not results should be targeted according to the audiences that the current user belongs to. More information about modern audiences and how to configure them.||False.|
|Enable localization||If enabled, the Web Part will try to translate the taxonomy term IDs found in result item properties and refinement values to their corresponding label according to the curent UI language. To get it work, you must map a new refinable managed property associated with ows_taxId_ crawled property and turn this toggle 'on': If enabled and depending how many items are currently displayed, this could be slightly decrease loading performances. To use translated values in your template, you must use the '