When creating solutions based on SharePoint search, you best always define the source ID of the Local SharePoint results source with each call. By providing that source ID with each request, you make sure that the results you expect for your solutions are always the same. Which ID? The Local SharePoint results source ID you are looking for is: 8413cd39-2156-4e00-b54d-11efd9abdb89.
I just got a question from someone who wanted to know how to retrieve all the Office 365 Group documents he had access to. When you are having a lot of groups in your organization, files could be spread across them. Search is in most cases the answer to finding your documents easily.
Last year I did a couple of session about how to improve the search experience in your environment. In this session, I highlighted a couple of simple things that mostly stay untouched and things that can be quickly implemented. One of these key takeaways was implementing synonyms. Configuring synonyms can be done via the thesaurus functionality and works on-premises differently than on SharePoint Online.
Last week I finally found some time to get my demo tenant up and running with hybrid search configuration. The new hybrid search experience eliminates the need of the result block. All results are aggregated together right now. So that means if you do a search query, you could get SharePoint Online results and on-premises results.
If you created your own display templates, you most probably have used the AddPostRenderCallback function. The AddPostRenderCallback function allows you to execute code once the display template completed rendering and this function can be used in every template (control, item, …). Now when you are creating your own refiner display templates and want to do something once all the refiners are rendered, the first approach would be to create a AddPostRenderCallback function in the refinement control template.