Tag Info

New answers tagged

0

You can do this in a couple ways. If you REALLY want to use a Display Template you can create a copy of the Default Item Template and then replace the body div with: <div id=”Item_PropertyList”> <!-–#_ if(!$isNull(ctx.CurrentItem)){ for (var key in ctx.CurrentItem) { var value = ctx.CurrentItem[key]; console.log(“Value: ” + value); _#–-> ...


0

SharePoint 2013 search result web part uses display templates. You can go to Search Service Application in central admin. Then open "Search Schema" to find all Managed Properties. If you want to test out, then click on Result Sources. Then "New Result Source", from the dialog use "Launch Query Builder".


0

Yes you can use Search Query to get data. Only thing you need to make sure is the data won't be real time. StartDate managed property is already available out of the box. Create a managed property to map crawled property ows_DueDate. Create a new result source based on the logic "DueDate=StartDate" For displaying result you can use result webpart ...


0

You need to map these columns to DateTime type managed properties like Date00 and Date01 (with refinable, sortable etc properties). Only DateTime can be compared with query (>,<,=, etc).


0

You can create extra property in the SharePoint User Profile not in AD, that used to identify the accounts which needs to exclude from People search.you can create a crawl rule to remove them from the results How to exclude Admin Acounts from People Search Result Remove Admin/System Accounts from People Search


0

You need to make a copy of the Current People Results scope and configure a new scope to hide the people that meet your rules. Information about managing search scopes is available Here I found this site and this site that seem to explain quite a bit about the customization of Search Scopes


0

Indexing your list columns will allow you to search on the columns that you want to display results on. Go to List Settings -- (under the columns section) click on Indexed columns. Create a new index on the column(s) you would like to search on. For example my list search box will first look for results on "Case Name" then "Case Number" AND then "CU ...


0

My requirement was to mix three types of content types. I created new result source with below query. {?{searchTerms} ContentClass=urn:content-class:SPSPeople} {?OR (({searchTerms}) ContentSource:WCFContacts)} {?OR (({searchTerms}) ContentSource:WCFAccounts)}


1

This is by design. You could modify the search result webpart to automatically append the * at the end. Not ideal for document search, but for people search its okay.


0

Couple of things to be noted. Extending a web app does not mean you get separate content, extended web application share same content database as Default Web Application. Extending Web application basically used where you want to implement different authentication to a different set of users. I.e you want claims windows on default zone and for intranet ...


0

Use the 'selectproperties' query string parameter


0

You can use the site data query to make it easier, its very similar to spquery. You can give the lists by using the Lists tag with guids of the list. Example: using (SPSite site = new SPSite("url")) { using (SPWeb web = site.OpenWeb()) { SPSiteDataQuery query = new SPSiteDataQuery(); ...


0

We found a solution allowing us to manipulate the Content Search web part in the following ways: 1) Append a "Show all" link to the web part's visual output 2) Add custom properties and use the values in code-behind. First, we created a new (non-visual) web part extending ContentBySearchWebPart. Then we overrode CreateChildControls, adding our link control: ...


0

I just changed the Application pool in Search Service Application I created. Earlier, I was creating a new Application Pool as "Search Admin Web Service" and "Search Query Web Service" but I am not able to understand how this Application pool could be an issue because in lot of articles and videos it is clearly told to create separate application pool. Can ...


0

You need to write the query as Write<="1/1/2012" Here is a good reference for search keywords for SharePoint 2010.


1

Technically, you are using People Search. I usually use REST for this, but there are analogous Properties in CSOM. You have to set the result source ID to the People Result Source. In your code above remove the HiddenConstraints and add keywordQuery.SourceId = new Guid('B09A7990-05EA-4AF9-81EF-EDFAB16C4E31'); If you really want to emulate the results you ...


1

If you are talking about the person group item on the results.aspx (Everything) tab, that uses the compact person item I believe. You can create new templates rather than change the out of the box templates. Here is the process: http://www.ableblue.com/blog/archive/2013/06/05/introduction-to-sharepoint-2013-display-templates/


1

If you are asking about display templates: /_catalogs/masterpage/display templates/search/item_person.js <- renders result panel /_catalogs/masterpage/display%20templates/search/item_person_hoverpanel.js <- renders hover panel


2

You can try using the below jquery: $(".ms-InlineSearch-Outline-Baseline input").val("Search People");


1

I don't know if you can choose to only hide some of them, as the setting for removing them is showing all or none. I always hide them and let the users refine their search in the search center. As a site collection administrator, navigate to site settings > under site collection administration > search settings. You have to deselect "Use the same results ...


1

You should be able to go to Site Settings then Search Settings and remove the options you no longer want.


0

Stupidly, I was crawling the old SharePoint 2010 MySite, not the new 2013 MySite.



Top 50 recent answers are included