New answers tagged

0

Simplify your life. Use a common Content Type for all 4 libraries. Then create a Result Source like ContentType=MyContent. Then apply the query to the Result Source. If you cannot create the result source then just add that query to your web part or rule. If you can't or won't create the Content Type then you can use Path, but IMHO that's yucky.


0

That is working as designed. You have to have search results to be able to "further refine" the results. The concept is to narrow down the result set based on attributes returned in the results set. No Results = No Refiners


0

If you are on SharePoint online or 2013 try creating a search result source: https://support.office.com/en-us/article/Manage-result-sources-fd8d6ac6-c5d0-454d-80a9-51580902b25d. This allows you to transform your search query so that only the metadata field is search, which should result only in items from your document libraries. There are also other options ...


0

here in short a description, what you have to do: First, go into your search service application and open the search Schema. Make sure, that your site column is a manage property and run a crawl. The second step is the modification of the display template. You find this file under master pages and can modify it to Display your value.


1

No, not without customization. On premises you could write a custom security trimmer that looks for the write permission after the query runs.


0

You should start by copying a display template that does most of what you want, like popup hover card, etc. They are stored in the Master Page Gallery under Display Templates. Then add your refinable property and then insert the property reference in the form ctx.CurrentItem.PropertyName The rest is just fighting JavaScript and HTML. Rename the copy of the ...


1

You could create a SSA in a test environment and restore the backups of the SSA databases. Then write some PowerShell to dump the configuration. That is the only way I can think to do it.


0

In your display template add the "refinablestring00" to the managed property mapping like below <mso:ManagedPropertyMapping msdt:dt="string">'Title'{Title}:'Title','Department'{Department}:'RefinableString00'</mso:ManagedPropertyMapping> In the code block you can get the value of the property as below, var department = $getItemValue(ctx, ...


0

Usually in this case the following should help: - stopping all crawls (if possible) - restart of Search Host Controller on each server which is used in topology - starting the crawls I don't know the reason why crawls go to never ending mode, however, this search host controller restart seems to be the best solution that is not as much influencing ...


0

Noderunner.exe (Microsoft SharePoint Search Component) is a component of SharePoint 2013 Search managed by the SharePoint Search Host Controller Service, and each Noderunnerprocess hosts one of the following Search components; Crawl Content Processing Index Analytics Query Processing Search Administration Noderunner.exe is the new executable of search ...


0

People properties (and BCS properties) have to be created at the tenant (or farm for on premises) level. I suspect that you created your properties in a Site Collection.


0

Just use a standard links list from SharePoint. Add link items to the list in the same URL format that you see on the search Results page. Like https://sharepoint/search/pages/results.apsx?k=keyword


0

If by "read" you mean "search" then you have to crawl the content. SharePoint won't do anything with the index itself, you have to direct SharePoint to crawl the same content.


0

I think all you need to do is: Give your html file a different name such as Control_CustomSearchBox.html. Inside this file change it's title to something different like: Custom Search Box. Add a Search Box webpart to your page and edit it's properties. In the Settings section change the Search box control Display Template to your new Custom Search Box. ...


2

If you go to Site Settings > Search Settings > Send queries to a custom results page URL, you can send your results to the Search Center using the Search Center URL property, thus: {SearchCenterURL}/results.aspx EDIT I believe the properties are as follows: Site Collection Search Center = SRCH_ENH_FTR_URL Site Collection Search Dropdown Mode = ...


0

I will give here some steps I did: I created my own refiner for the content types. I took the standard one and added the lines: if (ctx.RefinementControl.propertyName == "SPContentType") { var blacklist = [ "Comment", "Element", "Document", "Folder", ...


0

I use Chosen.js Easy to implement, and I used this week with a lookup with more than 500 itens, works really fast and easy. you will need: jquery-1.12.1.min.js chosen.jquery.js chosen.css


1

I know this is an old post, but I thought I may be able to shed some light on this subject. As a couple of folks pointed out above, the following syntax will access the refiners for a managed property called owsRoles. http://server/_api/search/query?querytext='Query text'&refiners='owsRoles' Make sure that the managed property is mapped to the ...


0

I have had issues with these crawled properties not being mapped correctly to Managed Properties by default. In Site Administration > Search Schema, this is what I have done: RefinableDate01 – This is a SharePoint provided Managed Property of Type = Date that is provided for configuration. It should be mapped to the Crawled Properties: ...


0

I tried adding one more managed property maped to Basic:15(Date and Time) crawled property and did full crawl. After full crawl page is throwing below exception "Your query included only common words and / or characters, which were removed. No results are available. Try to add query terms." But on the next day, after scheduled full crawl at night same ...


0

Unortunately I was not able to find the problem. Restarting the entire server solved my problem.


0

You can use following end-point. It can search users from all directories. var userSearchSuggestionEndpoint = "/_api/SP.UI.ApplicationPages.ClientPeoplePickerWebServiceInterface.clientPeoplePickerSearchUser"; HTTP post request is needed to get data from above end-point. Request payload is given below. var data = { queryParams: { __metadata: ...


0

To get AD users in Sharepoint you have to put filter as /_api/web/siteusers?$select=Id,Title,LoginName,Email&$filter=id eq 'Your Id'


1

You can retrieve it from the DataProvider object. Which is accessible from within your display template. ctx.DataProvider.get_currentQueryState() This returns an object which gives you the whole search query context, like: keyword, sorting, refinement, ... In your case you want to extract the keyword, which you can retrieve from the property like this: ...


4

You will need to perform full crawl. This will remove deleted sites from search. To crawl content that is defined in a particular content source, take the following steps: Go to Central Administration and then to Search Service application. On the Search Administration page, under Crawl, click Content sources. On the Manage Content Sources page, point to ...


0

Could be it is "trimming" what it sees as "near duplicates" ...Use Fiddler trace and look at HTTP - response raw ... Look for something like Trim or collapseSpecification":"DocumentSignature:1


0

You cannot do this in a single query. You would have to write multiple queries...something like. ContentType=InfoList Status=Active retrieve the Path to the containing Site. ContentType=PDoc DocType=AAA Path=Path from #1 You can do this in JavaScript or and App or C# Code depending on your skill level.


0

One possible solution, is to ask the administrator to change this using the administration tools on the server: Go to Search Schema, and check the sortable checkbox (and, if desired, also the refinable checkbox) for the managed property Title.


0

You mean ctx.CurrentItem.Path? It will spit out something like http://sharepoint/sites/sitecoll/Lists/listname/DispForm.aspx?ID=1 Why not set the href to ctx.CurrentItem.Path instead of #? Check this out for all the properties you can get: http://sadomovalex.blogspot.com/2013/06/enumerate-all-properties-of-javascript.html


0

One option is to create a result source in SharePoint and use KQL to not show items in the result source if they were not created by the user who is viewing the results. Adding this logic to a search query will only show content that was created by the user initiating the query: CreatedBy:{User.Name}


0

You can use the created by field and filter on that. As explained in detail here: http://en.share-gate.com/blog/filtering-content-with-sharepoint-user-properties-search Note: Normally I would not post answer's like this, but can't re-make the guide at work (blocks the images).


2

As mentioned by Mathew the managed property you are referencing should be text only. You need to have refinable, sortable managed property to use in your query. There are multiple refinable properties like refinabledate00 to refinabledateXX which are already available in site collection schema, you can re- purpose this property by mapping relevant crawled ...


0

You are probably better off creating a Query Rule for this. Use and Action Term like "Section 5 of policy" and then promote Section 5 as the result. This works particularly well if what the user is looking for is an individual document.


2

Automatically generated Managed Properties are always Text regardless of the base property type. If you want Date type you have to create it yourself either in the SSA or in the site/site collection.


0

You want to search for documents? Or Pages? Or everything? Are these things grouped by site or something? This question depends on your site structure.


0

MaxCharactersInPropertyStoreIndex=1 on a new managed property might do the trick, so it is limited to only storing a single character in the index (this should theoretically be available in PowerShell (but not in GUI).


1

I think there are four issues with what you are trying: Your managed property names cannot have spaces in them, i.e. presuming start date and end date are your list columns, you need to find the names of managed properties associated with them. So your query might become like this: Today >= "StartDate" && Today < "EndDate" You will need ...


0

Upon additional digging within the SQL database, I was able to locate the tables containing the search queries. The relevant SQL tables for the search results are MSSQLogQuerySummary and MSSQLogQueryString. MSSQLogQueryString contains a list of all historical search queries, along with the most recent date that keyword was used. However, ...


0

Typically, there's be warnings regarding support implications on accessing the SP databases directly but I since SP2007 is out of support scope, I think that's your default position now. The database tables you'd need are: - ANLDay ANLHistoricalSiteUsage ANLHistoricalWebUsage ANLHit ANLResource ANLUser ANLWeb You may also want to edit a stored procedure ...


1

Can you post the the next lines of the code? I'm concerned about the way you are trying to get the results agains the search service. And the SharePoint 2013 Search Query Tool is pretty fine and helpful to test this kind of query. EDIT: I looked over a solution that I did years ago, and I saw that a few other parameters were needed: KeywordQuery ...


1

The closest thing to what you want in the spirit that is consistent with SharePoint search experience is a search vertical in a search center. Essentially, you create a separate search page which is using a separate result source, which filters the search results the way you want, while also allowing users to enter a search query. In your case, you would ...


0

Correct syntax is: Path:URL KeywordQuery keywordQuery = new KeywordQuery(site); string strQuery = "*"; foreach (string strPath in allLists) { strQuery += String.Format(" Path:{0}", strPath); } keywordQuery.QueryText = strQuery + " (contentclass:STS_ListItem OR contentclass:STS_ListItem_DocumentLibrary)";


2

-For the finer you have to customise the search refiner webpart for the more details to search on the specific list visit this site


2

You need to change it as below contentclass:STS_ListItem OR IsDocument:True


2

Yes it is. Use the following query: {{searchterms} (ContentType:A) AND (ContentType:B)} I would personally use SPContentType:


2

Try using PowerShell commend Stop-SPServiceInstance -Identity Example Stop-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce Where is the GUID of the service. If you do not know the service GUID, you can retrieve a list of all services in the farm together with their GUIDs by using the Get-SPServiceInstance cmdlet. Or if this not works ...


-1

Go to service property. Change logon with wrong user password. Save it with disabled type. It will not start automatically.



Top 50 recent answers are included