Propagation time for centrally managed/defined Search Result Sources with web parts

Rene Wagner 1 Reputation point
2021-12-02T00:31:10.437+00:00

Hi,

To implement a more governed environment, we are planning to use centrally-defined Search Result Sources (i.e. defined in Central Admin) to provide results for some Search Result web parts on our sites. So we created the Result Sources and then added Search Result web parts and configured the query to make use of the Search Result Sources to display the relevant results. This all works fine.

Now I make some changes to the Result Source in Central Admin, but when I go to the sites where the web parts are defined it does not look like those changes take effect (at least not immediately). The question I have is -- if changes are made to the result source in Central Admin, what has to happen for these changes to apply to the web parts that use these result sources? Is there a job that has to run to propagate these changes out? Is there some other process that has to complete like clearing/updating the browser cache? Or something else one has to do to get those updates to appear in the sites?

Thanks

Microsoft 365 and Office | SharePoint Server | For business
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Echo Du_MSFT 17,316 Reputation points
    2021-12-02T08:00:10.057+00:00

    Hello @Rene Wagner ,

    Welcome to Q&A Forum!

    According to my research, when make some changes to the Result Source in Central Admin, you need to run Full Crawl again.

    Here is my test:

    1.Edit the Result Source in Central Admin

    154280-s0.jpg

    2.Start Full Crawl for the Content source

    154326-s1.jpg

    3.Go to the Search Center site (or site collection) Site Settings page as a site admin

    4.Click Result Sources, make sure this Result Source set as default. In my test, my Result Source named [Test1202].

    154411-s2.jpg

    154421-s3.jpg

    5.Go to the results.aspx and click Edit page. For example: http://sp:81/sites/search/Pages/results.aspx

    154398-s4.jpg

    6.Click "Edit Web Part" on the Search Results web part

    7.On the Search Reults windows, click "Change query" button

    154365-s5.jpg

    8.Make sure the value of "Select a query" is [Test1202].

    154422-s6.jpg

    9.Save and Publish this page.

    154327-s7.jpg

    Thanks,
    Echo Du

    =========================================

    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.


  2. sadomovalex 3,636 Reputation points
    2021-12-02T14:36:29.607+00:00

    in one of the previous projects (SP on-prem) we programmatically forced Full crawl during provisioning (when managed properties and result sources were configured) from PowerShell in order to have changes in place faster. Unfortunately don't have more details or examples already - it was long time ago.

    0 comments No comments

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.