Contents
2 ways to search for files in SharePoint. One of the great advantages of SharePoint over file shares is its ability to search and find the content you are looking for. Network drives, file shares, DropBox are great if you want to store content.
When you create a Search service application, the search system automatically creates and configures one content source, which is named Local SharePoint sites. This preconfigured content source is for crawling user profiles, and for crawling all SharePoint Server sites in the web applications with which the Search service application is associated.
How to search for files in SharePoint Maven?
By default, searches for all types of content, not just documents. So in other words, the search results will display any content (folders, events, tasks, contacts, whole sites and libraries) that match whatever keyword/term you typed in.
By default, in the first Search service application in a farm, the preconfigured content source Local SharePoint sites contains at least the following two start addresses: https://webAppUrl, which is for crawling the Default Zone URL specified for the existing Web Application (s)
In this article I will configure the SharePoint 2013 Search Service Application to include a File Share in its search results. I will first create a file share using Server Manager and will call the file share “resumes.”
Where is the search box in SharePoint 2013?
Despite its presence for quite some time (the feature became available in SharePoint 2013), not many users know about it or get to use it. Every Document Library in SharePoint 2013 has a search box located just above the documents themselves.
It is using the default service application proxy group which contains a search service application, and I have a few site collections. One of them has the top-level site of template based on the enterprise search center located at http://sharepoint.local/sites/search, which I will use to enter my queries.
Since the loading of a whole folder structure could be a bottleneck from performance perspective, to avoid that you might consider load on demand approach: Once the form is loaded, retrieve the list of 1st level folders and populate tree view: