New answers tagged

0

Trimmed security applies to the contents of the View, not the View itself. Do not create a View in the List, instead Create a Page (for admins only) with a ListView on it. You might want to create a separate Pages library so its easier to govern permissions, and exclude the content from being indexed by Search


0

We cannot target a crawl server to a particular content source.


2

Adding \\{searchboxquery?} to your Search Results Web Parts content source should work. If you are redirected to osssearchresults.aspx it sounds like you have changed the settings on the Search Box Web Part, make sure the setting; Send queries to other Web Parts on this page is checked, and your Search Result Web Part is marked as retriever.


0

It turned out that the "Item_Person_CompactHorizontal.html" contained two views, one for "single person result" and one for "multiple person results", so after modifying both views it worked...yeeey! ok... I cant accept this answer for two more days and Ill probalby forget to do so, but consider it accepted by me


0

This is not really an answer, rather a work-around, instead of copying an existing Query Rule, I created a new one following this guide


0

You are trying to crawl SharePoint 2013 farm in SharePoint 2010, AFAIK this is not gone happen. 2010 farm can be consumer not publisher for 2013. Note. This only works one way and a SharePoint 2013 farm can not consume services from a SharePoint 2010 provider). https://blogs.msdn.microsoft.com/alimaz/2012/08/07/service-application-federation-between-...


0

You don't really need to take a search box and set the value as in your answer, there's a more beautiful solution to this: Configure CSWP to filter results on the basis of Query string On drop down change event, change the query string value in the url Don't reload the page, rather just refire the CSWP query with the help of dataProvider.issueQuery()


1

Are you doing this on a Search Center site? or is it a custom site? Also, are you using a custom masterpage? I had problems before with some jQuery/javascript that for some reason were breaking the search results webpart and after the user tried to search it was displaying nothing. In my case, I had to use ExecuteOrDelayUntilScriptLoaded function for some ...


-1

I ended up using metadata navigation and filtering to achieve this.


0

You should set the max to 0. recycle the search host service. and run this cmdlet $UP = Get-SPServiceApplicationProxy | where {$_.TypeName -like "Usage*"} $UP.Provision() I don't know what the PS does, but it works.


1

This is very much an 'it depends' question! Work out how many items you'll have that will be crawled. For SharePoint 2016 the maximum supported number of items per index partition is 20 million (see Software boundaries and limits for SharePoint Server 2016, so divide the number of items you have by 20 million and multiply by 2 to get the absolute minimum ...


0

I found a tutorial yesterday that had one sort term in the post query. It took a bit of work to figure out how to do multiple terms. Here is what ended up working for me: 'SortList' : { 'results' : [ {'__metadata':{'type':'Microsoft.SharePoint.Client.Search.Query.Sort'}, 'Property':RefinableDecimal00,'Direction':0 }, {'__metadata':{'...


0

because this is in JS i passed in the date -30 days in the correct format. var date = new Date(); date.setDate(date.getDate() - 30); var dateString = date.toISOString().split('T')[0]; query = " (RefinableStartDate<=Today AND RefinableEndDate>Today AND RefinableStartDate>\"" + dateString + "\")";


1

You can enable sorting using below keywordQuery.set_enableSorting(true); var sortproperties = keywordQuery.get_sortList(); sortproperties.add("Write", 1); //0 = Ascending


0

The properties you are looking for are already automatically created for you by SharePoint, "EntityName" and "EntityNamespace". You don't even need to create the managed properties and map them. Take a look at Search Service Administration page in the Central Administration and "Metadata properties" section.


0

SharePoint treats all "items" as single entities. The only place where you can specify a different behavior for Parent-Child relationships is via the BCS. So you have two options. Write a bit of JavaScript in a Display Template that, when the "Sassy" result is returned it fetches (pun intended) the linked items from the other list. This is pretty trivial ...


0

First off, I don't have any experience with MSS beyond the SharePoint components. Having said that you SHOULD be able to just create a new installation on your target and then "upgrade" or "attach" the existing databases from the previous installation. I'd look for info on doing a 2008 to 2010 "upgrade" and follow the guidance. (This is how we'd do it with ...


1

Did you create a Managed Property for "A"? If not your query will not work. If "A" was created as a Site Column, SharePoint will create an "Automatic" Managed Property based on the name and data type. For example, if "A" is of type TEXT you could try AOWSTEXT:"Text in A" There are tons of examples on how to create Managed Properties if you search for it.


0

A crawled property is automatically created for the site column during a crawl. The name of this property is generated by removing spaces from the site column name, and adding a prefix. The prefix that is added varies depending on the site column type. in this example, we get the following crawled properties: ows_q_NMBR_MyCustomID A managed property is then ...


0

Make sure you put the People Properties in the PeopleIdx. When you create the managed property choose Advanced and change the Index to PeopleIdx.


0

I fixed this by randomly dragging around some of the divs in the Sharepoint Editor. It's kind of broken now and won't let me add anything else to the page or make any further layout changes without all the webparts becoming corrupt, but it worked!


0

You can add a table on the page and you can add the CEWP in one of the columns. You can fix the width of the column so that the CEWP is exactly below the search box. Good luck!


0

Try if these steps helps you Go to Central Admin -> Manage Service Applications -> Search You will see a link to your Content Sources. If you edit that it will give you the opportunity to setup a schedule for both Full and Incremental indexing You can run a full crawl, once completed you will have results if everything is configured correctly


0

Do you see any error on the screen? Probably a consideration of index reset in Central Admin, and run a full crawl.



Top 50 recent answers are included