Tag Info

Hot answers tagged

4

I don't think you can get rid of the textbox. But the other two requirements may be solved by modifying the Refinement Panels Filter Category Definition. Here is the valid option for the Refinement Panel XML Schema. SortBy="Name" SortDirection="Descending" should give you the ordering you need. MaxNumberOfFiltersToDisplay="50" ShowMoreLink="False" should ...


2

You can, if you edit the refinements web part Xslt. You can start the exploration here: http://www.sharepointanalysthq.com/2010/06/sharepoint-2010-search-refinement-panel-options/ or http://msdn.microsoft.com/en-us/library/ee819920.aspx. You need to add something like <CustomFilter CustomValue="Video"> ...


2

You can set the Title attribute value to the name of the field you'd like to display (spshjobtitle in the example below). Any managed properties explicitly listed this way aren't going to be included again in the generic Managed Metadata Columns category. <Category Title="spshjobtitle" Description="Use this filter to restrict results to a ...


2

The title property of your XML entry is very important. Place the following XSL into the XSL property of the refinement panel, to view the raw XML, returned by the search <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" ...


2

It is possible to define a SharePoint column (e.g. Categories) as a managed property. You can then modify the "Filter Category Definition" of your refinement panel. It is outlined in that blog post in a little more detail: http://www.ableblue.com/blog/archive/2009/12/09/adding-search-refinements-in-sharepoint-2010.aspx


2

This puzzled me for a while as well but I remember playing around with different settings and I believe this solved it for me: <Category Type="Microsoft.Office.Server.Search.WebControls.ManagedPropertyFilterGenerator" MappedProperty="MyMappedPropertyName" /> So I changed the type to ManagedPropertyFilterGenerator and used the associated ...


1

Can you post the managed property settings? Have you set the refiner property when you created the managed properties? If not try enabling that by editing the managed property and running a full crawl.


1

Steffen, you could do the following: do a webservice call to the search service, query each domain/username and retrieve it's displayname. Replace the refiner display values with the returned displaynames. But I do think that the displayname should be indexed, too. you might investigate it a bit.


1

If done the correct way, the refinement web part acts according to the xml returned by the core search results web part... Look at this blog for more info. This quote is from the Kjell: "The nice thing about using the built-in query manager this way, rather than running your own KeywordQuery and providing your own result XML local to the custom web-part ...


1

Yes and no. So You can implement your own Refiner inheriting (1 & 2 ) from http://www.threewill.com/2012/04/custom-search-refiners/ or http://www.sharepointanalysthq.com/2010/10/custom-refinement-filters-in-sharepoint-2010/ Use something like this (use MaxNumberOfFilters and NumberOfFiltersToDisplay) <Category Title="Skill" Description="The skill ...


1

Ofcourse you also need to change the file types which get crawled. Go to the Search Service Application within Central Administration. In the left navigation section Crawling, click File Types. Add New File Type for wmv and avi. Perform a full crawl. Now the media files should appear within the search results.


1

Are you provisioning Taxonomy Fields yourself? In that case, remember to also provision a Hidden Taxonomy Field, and the TaxCatchAll and TaxCatchAllLabel columns and event receivers (if you are provisioning a list definition with these columns). Outlined in great detail here. Taxonomy Columns not showing as refiners is a known problem if you skip these ...


1

Try increasing the "Number of Categories to Display" refinement web part property value from the default 6. In standard out-of-the-box web part configuration, 5 static categories such as Result Type, Site, Author, Modified Date and Company are displayed which only leaves room for a single taxonomy field.



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