Tag Info

New answers tagged

0

You could use the list Guid like explained here: http://www.eliostruyf.com/retrieving-list-library-name-search-result-display-templates/


0

For excluding results you can use following query {searchTerms} -Path=https://example.com/sites/test/DeptSiteDec2014/Lists/WorkFlowHistory/*


1

Yes. These type of queries are possible. You can do this by two possible ways Edit the Search Result WebPart and change the Query Criteria to query particular library By Creating a Result Source to query particular library For Creating result source - Check this blog ...


1

Please try below code: <xsl:choose> <xsl:when test="srportalurl!= ''"> <a> <xsl:attribute name="href"><xsl:value-of select="srportalurl" /> </xsl:attribute> <xsl:value-of select="srprojectname" /> </a> </xsl:when> <xsl:otherwise> <xsl:value-of ...


0

I found this which helped me solve the same problem http://thesharepointlife.com/2013/04/sharepoint-2013-search-not-display-all-results-2/comment-page-1/#comment-488 Quote: Export the Search Results Web Part from your page. Open the .webpart file in your favorite editor. Search for “Trim Duplicates”, you will find it as part of the DataProviderJSON ...


0

That depends on how Ranking is performed. The search engine calculates the relevance rank, that is to say, the order in which the search results for a query appear. The ranking model is at the core of this calculation. In most cases, you can influence relevance by using the available SharePoint 2013 ranking models in combination with query rules without ...


0

You need to find out which is the crawled property for this metadata and add it to the ExcludeFromSummary managed metadata property. Don't forget to start a full crawl after you modify the property.


0

I found it by my self. On the left menu you have the link "Data Sources". Here you can add an xml data source which will be visible in the datasources list.


1

You can use following code in the display template <div title="_#= $htmlEncode(line4.defaultValueRenderer(line4)) =#_" id="_#= line4Id =#_"> _#=STSHtmlDecode(line4.value)=#_ </div> Source - https://ingessharepointnotes.wordpress.com/2014/03/04/sharepoint-display-templates-display-enhanced-rich-text-field/ Another example var desc = ...


0

Hi Tom it's hard to find documentation for this but at the end I resolved using this pattern: resultspage.aspx#Default={"k":"*","r":[{"n":"owstaxIdYourManagedProp","t":["cf32e33f-7ca2-470d-956b-29368e54e736"],"o":"OR","k":false,"m":{"cf32e33f-7ca2-470d-956b-29368e54e736":"TermName"}}]} It's important to note that: k:* basically it means "all documents" ...


1

These columns need to be mapped from crawled properties (the on that the search have found) to the managed properties. This mapping won't me made automatically. How this mapping can be done and what the difference between mapped and crawled properties is can be found here: The search schema in SharePoint 2013 Manage search schema in SharePoint 2013 You ...


0

I am not a RegEx expert. I don't know what #1 is, but #2 Is a Phone Number match on the "Local People Results" Result Source and #3 Is an Expertise Match on the "Local People Results" Result Source. For any of these rules you can use the Query Rule tester built into the Manage Query Rules page. Select a Context and then enter a query like "512.555.1212" and ...


0

How to change the way search results are displayed in SharePoint Server 2013 about the naming conventions for automatically created crawled properties and managed properties (How to display values from custom managed properties in search results)


2

When working with a Display Template you have to request Managed Properties from the Context of the current item. The general process is: Crawl content Map crawled properties to Managed Properties Crawl Content again Create a new Display Template (often by copying an existing template) Add a reference to your custom managed property in the display template ...


1

Another option would be to add a content query webpart in the page - edit webpart - click Change Query - set keyword filter as Query from the search box - give path:Your library path Apply and save the page and try it out. You could refer this blog article for more information on configuring the content query webpart: Configure Content Query Webpart Edit: ...


1

You can make use of query string filtering. Create a new view for the document library and set filter to use {FilterQueryString} and apply necessary condition Create a new wiki page and then add the library webpart - Then set the view = new view create in step1 above In home page edit the page and add a new Script Editor WebPart and use <script> ...


0

Use an Image Library or an Asset Library. Images don't render thumbnails from a Document Library by default. You have to mess with the display templates if you use a document library.


0

You can always test with examples to try to understand the RegEx. I often use an online RegEx tester for this, for example https://www.regex101.com/. Here there is a list of operators for search RegEx in Sharepoint 2010. They will be that same for 2013 and most likely are the exact same ones as the standard RegEx syntax: ...


2

What you need is to create the UL and DIV element in the control template and push your content in it via the item template. Now because you are working with display templates, this can only be done onces the rendering is complete, because at that time, the HTML is placed on the page. My approach is to add your list items and description values to two ...


0

You need to some sort of customization, in order to see image preview in search result. The solution is to modify the hover display template that is being used for default items. This can be easily performed using SharePoint Designer 2013. Check this blog post for complete steps & code: SharePoint 2013: Image Preview in Search Results - Part I


1

you need to customize the item display template, Go to Design Manger and then Go to Design Templates, download the item display template and then you can modify it and save it with a new name. here you go with an code example. ...


0

It looks like the error is related to <Column Name="ContentClass"/>. The problem seems to date back further than I expected. I am not 100% sure but it seems changes made by other people to the search criteria (Scopes, metadata, etc.) caused this specific type of information to be lost and no longer related to the results. I simple modified the core ...


1

I figured it out. Went to the Result Source Launched the Query Builder Selected Show All Managed Properties and then selected ContentSource Select Not equals and selected a manual value and typed in the content source that I wanted to exclude.


2

You can add two pages and two search verticals. The search criteria you should use is Edit Content Search WebPart Click Change Query Select a query = "Result Source" from the drop down. Here is a walk through http://www.sharepoint24x7.com/2014/10/01/article-customizing-sharepoint-2013-results-using-result-sources/


0

Yes you can extend the CoreResultsWebPart and create a new webpart. public class ElevatedSearchResults : Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart { .... } Now one problem with your approach is, if you elevate the code then all results will get displayed which the current user is not suppose to see. Also if the user who tries to ...


0

your control display template needs to be changes to like this: <!--#_ if (!$isNull(ctx.ClientControl) && !$isNull(ctx.ClientControl.shouldRenderControl) && !ctx.ClientControl.shouldRenderControl()) { return ""; } ctx.ListDataJSONGroupsKey = "ResultTables"; ctx["CurrentItems"] = ...


2

You are including four scripts to be used in combination with your display template. I think that your problem is related to the fact that a script is not yet loaded. It can happen that a script fails to load, or that it has not yet been loaded. $inlcudeScript does not ensures that your scripts are loaded at the moment you want to execute your code. My ...


0

You could additionally delete the results.aspx page - but an advanced user can simple use the api (or the search query tool) to get the results. Your request sounds more like security by obscurity - please clarify if this answer is not sufficient.


1

I think the problem relies on the nature of the search results web part. When you access the page from the browser the search results are returned from the server in JSON format. You can check this by using Fiddler and checking the response of the ASPX page. For obvious reasons, the crawler tends to ignore the contents of the "script" tags, thus not ...


0

Under 'Site settings > Search and Offline Availability' ensure that 'Always index all Web Parts on this site' is selected under 'Indexing ASPX Page content'


1

There is an OOTB result sources called Documents, you can use that to limit the results to documents. For lists, create a result source with query like this: {searchTerms}contentclass:STS_List For list items, create a result source with query like this: {searchTerms}contentclass:STS_ListItem Check this article: ...


1

Create result sources to limit the search results to the subsites only with the query like this: {searchTerms} path:http://sitecollection1/subsite1 Check this article: http://techmikael.blogspot.in/2013/04/limiting-search-results-in-sharepoint.html



Top 50 recent answers are included