12

If you export the web part and locate the JSON string that contains the "refinerConfigurations" you can change the "useDefaultDateIntervals":false and then set your own intervals like "intervals":[-365,-180,-30,-7,-1]. Dates in the past are negative and the future are positive. If you don't know how to export and import a web part let me know and I'll add ...


4

It's just CSS. Here is the snippet showing the inline style. I use inline-block rather than float as it gave me the organization and flow I needed for the wrapper divs. Let me know if you want the whole file and I'll post it for you. <div id='Value' name='Item' style="width:25px;height:25px;border-radius:3px;display:inline-block;"> <a id='...


3

It's not listed in the Boundaries and Limits document, but it does appear to be a hard limit. Though it is only enforced by the UI. You can use F12 developer tools to remove the "disabled" attribute from the button and add more. I tested and added 23 through the UI. The other approach would be to export the web part and add additional Managed Properties to ...


3

When was the last time you ran a full crawl since this issue? I'll be clear, I don't think that's the issue but managed properties (the refiners) are very unique and a full crawl is needed before you can even search against them. I wouldn't be half-surprised, as unbelievable as it sounds, that you would need to do a full crawl for the refiners to show the ...


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" encoding=...


2

XML is case-sensitive. Change the case of 'NLNAgendaPointDecision' and 'NLNAgendaPointKeyword' to lower case so that it matches the three you can see


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 ...


2

I figured a way to do this. I created a new column called "Order". The order column contained unqiue numeric values in the order to be sorted in. Then I created a new calculated column called "OrderBy" which took the "Order" & ":" & "Title" column. In search schema I associated a refinementstring to this new column. I then created a custom Display ...


2

Have you set the "Sortable" attribute for your Order Managed Property and then performed a full crawl?


2

This is not possible - the searchbox overrides the refinement. The idea behind it is: The end-user starts searching by using a phrase/keyword in the textbox - then he refines the result set with the refiners.


2

first you need to edit one of your refinement web parts.Change web part query. Allow this Web Part and other Web Parts with the same query ID to display results from the same query. Under Results Query Options, in the Cross-Web Part query ID box, select User query. All other selections do not give results. You need to make your refinement panels to ...


2

I encountered the same error a few days ago. Reported it to MS Support and they told me there might be a bug in SharepointOnline which causes the Managed Properties page to default to the incorrect level of site instead of sitecol So avoid using this URL _layouts/15/managedproperty.aspx?property=RefinableString00&level=site And simply use this URL ...


2

By default if you have a long refiner name you get the following output: The refiners are set to a width of 160px. So if you want to show the whole refiner, you have to change the width via CSS of these refiners. When changing the width, this will have an impact on the whole search page. A better approach would be to override the ".ms-ref-ellipsis" class. ...


2

Search Results web part can be configured with pre-built queries by editing the web part properties and specifying the query. You can use * as query which attempts to return all matching results.


2

I used css to hide it, that seemed to work okay but I am sure there are better solutions out there. h2.ms-displayInline a.ms-ref-name{ display:none;} Best of luck.


2

I would go for option number two as I did something similar in the past. It requires some development, but in the end, it is easier to maintain. The approach of the article you linked might work, my approach back then was different. In your refiner display template where you loop over all the available refiners, you split the values based on your delimiter. ...


2

You are missing one approach. If you know all the possible values you can use entity extraction using dictionaries to scan that mp with a multi-value, and have it populate to the WordCustomRefinerX managed properties. If that's not an option, I would go with your options in the order you list them. For the display template option you might want to add logic ...


1

It is not a bug. This is by design. A Display Template "~sitecollection/_catalogs/masterpage/Display Templates/Filters/Filter_SliderBarGraph.html" is responsible for displaying the refinement Panel. The Display Template gets its parameters from the Web Part. When you export the "Refinement Panel" Web Part, you will see this section: {"propertyName":"...


1

You can just create a web part page and add the necessary search web parts. Search Box, Refinement and Results are just web parts. The query can be passed on the query string or you can include a link to this page.


1

It looks like you are on the right track with the SelectedRefinementControlsJson propety. If you pre-configure and export a refinement webpart you can see how it populates the refiners. Here is a default export example. <property name="SelectedRefinementControlsJson" type="string"> {"refinerConfigurations":[{"propertyName":"FileType","displayName":...


1

The odd time shows up because FAST tries to automatically create 'bins' to put your search results in when you don't tell it exactly how... You said you have many records that have an uploaded date of 21 and 22 August -- FAST figured out the way that it felt like partitioning your results would be to put them into two separate bins with a dividing line ...


1

I think in your refinement panel Xsl, uploaddatedt property is defined as Range Property and not Simple Category. Regarding your first question you already said you have items with that date, So you will get that data only the format that you are getting is weired and to change that you need JavaScript to xsl functions And your next query could be solved ...


1

According to XSLT Global Parameters you could utilize the following global parameter: LCID -The value of System.Threading.Thread.CurrentThread.CurrentUICulture.LCID in string format. The following example demonstrates how to render the image from a language specific folder: <xsl:template name="NewGif" ddwrt:dvt_mode="body"> <xsl:param ...


1

Actually the custom file type extensions which we add to the central admin will be available in the file types when we preview the refinement panel. But the filetypes what we see is different, we see user friendly names for that. Say for xlsx we see Excel and for ppt we see PowerPoint and so on. So i checked the display template for the refinement panel. ...


1

I believe it's an artifact of choosing Decimal. I ended up mapping mine to Integer and it worked fine. In my case I did not care about the values below the decimal. I you need them you could always create a custom refiner that handled the values formatting them the way you liked.


1

You'd need to implement or buy a custom display template for your managed metadata refiner. This would allow you to modify the query sent to the search results webpart when a parent term is clicked to include those results tagged with its children instead of just with it alone (using the {Term.IDWithChildren} variable) To avoid confusing users, you may want ...


1

Actually separators are not used any longer in SharePoint 2013. The multivalue field needs to be populated using a List of items, e.g. List<string>. I'm using Content Enrichtment to populate my field using Property<List<string>> ; a good example from Microsoft: How to: Use the Content Enrichment web service callout for SharePoint Server ...


1

A quick Google search turned up the following article with sample code on creating a custom date range refiner. On the positive side it can be done. On the negative side, it seems like you will be creating labels instead of using the neat slider control. http://blog.ithinksharepoint.com/2013/09/27/building-a-sharepoint-2013-search-refiner-with-custom-...


1

We ran into the same problem. I have heard that FAST Search will respect the hierarchy and filter results as you would imagine it should work, but we are using SharePoint 2010 and SharePoint enterprise search. Our hierarchy was Make/Model/Series, and our solution was to have one "main" Make/Model/Series field that appeared on forms, that the users ...


1

This is an old question, but I'll add my answer anyway for future reference. I believe that the the fields are not displayed correctly because the use of PropertyDef-tag inside the ResultType-tag. The correct tag would be PropertyRef. So instead of this: <ResultType DisplayName="All Results" Name="default"> <KeywordQuery/> ... ...


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