Configure modern search results to search all of your organization (rather than the current site)
Hey everyone, We heard from many of you the need to be able to change the scope of your modern search results pages. When you create a new communication site or team site in SharePoint Online today, and type into the search box, you are taken to the modern search results page. This page shows results from your current site by default, and allows you to expand the scope of your search to the hub that the current site is associated with (if there is one), or to the whole organization. But there is a desire for being able to change the behavior to always search over the whole organization, or across the hub a site is associated with, without needing an additional click, especially if the site in question will be used as a modern landing page for your organization. I'm happy to say that with the latest version of the SharePoint PnP PowerShell extensions, it is possible to run a simple command as the site owner, and make your site use the organization, or the hub scope by default. To change this setting: 1. Start PowerShell in administrator mode as you will be installing the PnP extensions. 2. Run the following commands to in this order: PS C:\WINDOWS\system32> Install-Module SharePointPnPPowerShellOnline # If you previously had installed this module, you may need to use the "-Force" parameter to install the newer version. PS C:\WINDOWS\system32> Connect-PnPOnline -Url https://contosodemosg.sharepoint.com/sites/Strategy -UseWebLogin # this will prompt you to sign into your site. Use the site owner credentials to sign in PS C:\WINDOWS\system32> $web = Get-PnPWeb PS C:\WINDOWS\system32> $web.SearchScope = 1 # 1 for Tenant, 2 for Hub, 3 for Site, 0 for default behavior PS C:\WINDOWS\system32> $web.Update() PS C:\WINDOWS\system32> Invoke-PnPQuery After running these commands, the site will start to show results from the whole organization. To go back to the default setting, run the commands again with the value provided to "SearchScope" parameter to 0. To search across the Hub, use 2 as the SearchScope value. We will be providing a way to set this setting using the UI in a future release as well. Updated in April 2020 to reflect the ability to search across Hubs.Unable to see documents when searching by folders in Modern Document Libraries
Hi everyone, I am seeing some odd behaviour with modern document libraries when you try to search for content stored in folders. Lets say you have the following structure in a document library: Folder named "James" File named "P45" File named "P11D" Folder named "Gary" File named "P45" File named "P11D" Modern Experience: If you do a search in the "Search" box in the top-left corner for the word James then you will see the James folder returned. If you then click into the folder you don't see any documents shown such as the P45 or P11D docs, with a message saying "No items match your query". Classic Experience: If you switch to classic experience and do a search for James in the "Find a File" box, you will see the James folder returned. When you click into the folder you will then see the two files, P45 and P11D. The modern search is appears to be doing a search on items that contain the phrase "James" in the filename or in the document, where as the classic experience is doing more of a filter on the current items being displayed and then allowing you to see the child items in that folder. If you search in a modern experience, you can then see the child documents if you remember to clear your search query from the search box, or if you remember to not press the Enter key at the end of typing your search query and use either the mouse or keyboard to select the folder from the auto-suggestions. If you do choose a folder from the auto-suggestions then this opens in a new tab taking you away from where you were originally working. This has been reported by users and clients as a significant pain in the user experience when searching for content and is causing push back on adoption of SharePoint. Have you guys seen this before? Cheers,
Collapsible sections: Linking to auto-expand a section and non-effective Search
As already discussed in some previous threads collapsible sections have a lowered functionality when being linked to; even though Section headers have anchor links, these have very limited function as they only bring you to the overall page with all sections. This is especially useless when you are trying to keep the page clean by collapsing your sections by default. The thread presents a workaround by adding an additional header within your collapsed section, which will open the section on landing, but you will end up with a redundant header: Collapsible section name Collapsible section name (redundant) This is less than ideal and means always repeating your section names, it also doesn't work properly when you want to link from one section to another on the same page. Additionally, if you try searching your Site for a keyword contained in one of the sections, not only will it not bring you to the paragraph containing the keyword, it will only open the page with all sections collapsed and with a focus on the very top of the page. Therefore there is no point in searching when you decided for Collapsible section organization for your pages, the Sharepoint basically tells you "It is somewhere on this page". You still need to expand each section and either scan the page to find the searched keyword, or use Ctrl+F. Is there a way to report this to the actual developers so they can implement web functions that have existed since 1991? anchor link opens the page, moves the section title to the top of focus and opens a collapsed section (perhaps this could be a toggle in section options) clicking a result in Sharepoint search does the above and additionally highlights the searched keyword within the section Thanks for reading.
SharePoint Communication site search
How to change the communication site search scope from default "current site" to "all sites"? It's still not supporting search center configurations from search settings. Why I have two different experiences on search? When searched from any communication sites - its redirected to https://contoso.sharepoint.com/sites/contosoportal/_layouts/15/search.aspx?q=team When search SharePoint home app - its redirected to https://contoso.sharepoint.com/_layouts/15/sharepoint.aspx?q=team&v=search Give me option to redirect my queries to classic search center directly from communication site.NEW SharePoint: SearchQueryTool (Online)
Hi everyone, I've developed a new web based SearchQueryTool. If you're interested you can read more about it here: https://dev.to/niklaswilhelm/devtools365-sharepoint-searchquerytool-online-3jed Or directly try it out: https://www.devtools365.com/sharepoint/searchquerytool Remarks are welcome. Happy Search!
Microsoft Search KQL question
I want to create a custom search vertical in Microsoft Search that returns People results only. I have created a new Search Vertical and added the following KQL in the Query option but it doesn't return any results. ({searchTerms})(ContentClass=urn:content-class:SPSPeople) Have I got the syntax right or am I missing something else? Any pointers to help solve this would be much appreciated. Thank you, Steve
Modern News Pages and Highlight Content Web Part
I have created a site column called BlogVersion (choice) and added this column to my site pages library. Most of the pages have the choice column set to "Old" and only the current blog page set to "Current". I am trying to use the highlighted content webpart and looking for a managed property which contains blog and the webpart shows BlogVersionOWSCHCS but when I put a value of Current, nothing shows up. I have tried to re-index the library (office365) and will wait to see if there is a change but am I missing a step?Enable full-text search for non-std file types (like .json files) in Sharepoint in Microsoft 365
If I have a .json text file in a Sharepoint document library, Sharepoint in Microsoft 365 can't find results when searching for a phrase in the file. When I upload the same file but with a .txt file extension, allow time for it to be indexed, Sharepoint can find *that* .txt file when searching for the phrase within the file. I want Sharepoint to index .json files the same as it indexes .txt files. How can I associate any given file extension as a Text file capable of being full-texted indexed like .txt is? I'm imaging of list of file extensions somewhere, where I can add .json, but can't find anything like that.
