2

If there are a limited number of locations you can use search. Who will be the user? A "power user" who could be shown how to write search queries? If not, A friendly UI will take some additional work. Search: (path:"https://yourDomain/HR/policies/external" OR path:"https://yourDomain/HR/general document/external") AND isdocument=1 Search can be used ...


2

(From MS official Documentation) When you use words in a free-text KQL query, Search in SharePoint 2013 returns results based on exact matches of your words with the terms stored in the full-text index. You can use just a part of a word, from the beginning of the word, by using the wildcard operator (*) to enable prefix matching. In prefix matching, Search ...


1

SharePoint search was designed for documents and words. Your Titles like "8841271.030-2017" contain stop characters and word breakers. You can play with it for weeks and never get the "SQL Style" querying that you seek. You may want to revisit the end user requirements and try to break them of the file name type search. Find other metadata that they can use ...


1

That article outlines the right approach IMO, so let's deal with the objections :) Require to manually map the folders/sub-folders. and users might create a folder and forget to map it. Configure metadata the field as required. Will give you a nice "information required" audit view, and annoy anyone who has incorrectly configured their folder. To prevent ...


1

You can create your own search result pages as search verticals. In these pages, you can edit the search query per your requirements.


1

You can specify the Search Scope in XML of Advance Search Web part. Export the Advanced Search Web part Open the web part file in a text editor You will notice something like this <ResultType DisplayName="All Results" Name="default"> <Query/> <PropertyRef Name="Author" /> <PropertyRef Name="Description" /> <PropertyRef ...


1

Here's an example of how to do it in C# SearchServiceApplicationProxy proxy = (SearchServiceApplicationProxy)SearchServiceApplicationProxy.GetProxy (SPServiceContext.GetContext(SPContext.Current.Site)); KeywordQuery query = new KeywordQuery(proxy); query.ResultsProvider = Microsoft.Office.Server.Search.Query.SearchProvider.Default; query.HiddenConstraints ...


1

I am sorry I just got the answer. It is because I edited the search query on results.aspx. The original query is: {searchboxquery} I changed to: {?{searchboxquery}} It will avoid result.aspx return wildcard result when type in nothing (i.e. /sitespages/results.aspx?k= will return all items within the search result source) After I remove the questionmark ...


1

It looks like search may not properly be setup on your farm. My first recommendation would be to verify that search works. The easiest way, in my opinion to verify search is to add the search results webpart to a page and verify that I can pass in the search query string to get results. www.myspsite.com/pages/SearchPageWithResultsWP.aspx?k=...


1

You don't need a web part for this. You just need a simple form that can: Create a simple form that collects the information you desire Create a query string with the data Redirect the user to the Search Page with the Query String appended to the URL. For example by adding a button to the page. For example: Collect ContentType and Author Name "ContentType=...


1

First please check whether search service application is set up. You can create enterprise search site from site templates when creating site. Then when you search you will get advanced search pages Edit 1 there are 2 ways you can do this.First is use same page which Microsoft is using which is as follows 1)advanced search page layout is in the ...


1

I had created a result source a while back and i did not include the return of txt file as part of the query. I just assumed I was returning txt files. Even though I added the result type for txt in the drop down of my advanced search web part I still would not get any hits because the result source query didn't include txt. All is working now that i ...


1

Another way when you have an Enterprise Search Center (or one of their search result pages) would be to adjust the query itself to something like this: This lets your users search for filenames without the need for you to deal with an additional result source. I however highly recommend looking at the blog posted by John (this post and all others from ...


1

You can restrict the search result only to this scope. Enterprise or basic search center would work fine if you create specific result source / search verticals. You can look into creating separate Search vertical for the same. how-to-add-a-custom-search-vertical-to-your-search-results-page-in-sharepoint-2013


1

I don't think you can do it by editing any of the web part properties. I tried hiding them with a bit of JavaScript in SPO and that worked fine. Your element id may well be different if on-prem... window.onload = function () { var foo = document.getElementById("ctl00_ctl40_g_a5766bae_2940_4457_96b6_daed259dab6f_ASB_PS_olb_0"); foo.options[2].style....


1

If you are not seeing advance search webpart in webpart gallery. Below is what you can do. Go to the Advanced Search page in the search center site. Edit the page and Export the Advanced Search Web Part. After saving the exported web part file to your computer, go to the Web Part Gallery in the top level Site settings. Click "Files" in the ribbon tabs and ...


Only top voted, non community-wiki answers of a minimum length are eligible