Hot answers tagged

5

Could very well be a problem related to "TrimDuplicates". This functionality is activated by default and tries to remove duplicate items from your search results. You can turn it off by editing the query with the query builder, going to Settings and turning off duplicate trimming, as per your comment :)


4

Use the managed property called ows_YourFieldName not ows_taxidYourFieldName The taxid one will include the GUID, unwanted for Refiners. This is my experience at least. Found another post stating the same here: ...


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

To make this happen you need to add a Managed Property in your Search Service Application. You find the existing Managed Properties in the Queries and Results section named Search Schema. Type isDocument in the filter section and hit the green button with a white arrow. You should see this: It tells is that the isDocument managed property returns all ...


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


2

What you can do is use the IsDocument property: IsDocument:0 Here


2

You need to map the crawled property for the column to one of the existing RefinableString... managed properties. This is due to a limitation in SharePoint Online where you can not mark additional managed properties as refinable (as you can do on prem) Detailed instructions here: ...


2

I think you can make a call like this to get the values for owstaxidmetadataalltagsinfo refiner: http:// siteurl /_api/search/query?querytext='*'&refiners='owstaxidmetadataalltagsinfo' You will get some values with this format: L0|#036f7c08a-0176-47e9-9d70-070291ce0e32|Data Warehousing


2

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

I wound up saving all of the items in the site using the following script, and that did the trick. $totalCount = 0 $web = Get-SPWeb "http://dev.site.com" $list = $web.Lists["Documents"] foreach ($listItem in $list.Items) { $listItem.Update() $totalCount++ Write-Host "Item saved: " $totalCount } Write-Host "Total Items Updated = " $totalCount ...


2

According to MSDN, IncludeRefinementResults, Refiners, and Refiner elements apply only to FAST Search Server 2010 for SharePoint.


1

I would go for the following option map the (content-)language crawled property on a (new) meta-data property. As you are using Fast, it is not possible to use a custom filter with a value mappingtype (http://msdn.microsoft.com/en-us/library/ff625185.aspx). Maybe you could try a range-type, as you are getting back numbers, but I am not sure. If you are ...


1

I had the same problem. Please check http://social.technet.microsoft.com/Forums/nl/sharepoint2010setup/thread/1485e82a-49f6-44d7-92e1-649be85352ad "You can set the search path for MySites by going to Central Admin -> Mange Service Applications -> Click on your User Profile Service Application. From here under the MySite Heading the first option is Setup My ...


1

I think that will be hard. My best guess: Create a separate search center/search page per language, and map your refiners on the locaized values. You should use a valuemapping + customfilter for this one: http://msdn.microsoft.com/en-us/library/ee819920.aspx Using this technique, you can map the value 1 on, for example, red, rojo or rood. It requires you to ...


1

Look at this Codeplex-project: MUI Search Refinement Panel


1

I can't see a way of doing that with the out-of-box functionality. However, you could write your own refinement filter generator. Essentially, it's about subclassing RefinementFilterGenerator


1

You have to set CustomRefinementIntervals property on KeywordQuery


1

OOB SharePoint 2010 does not have multi-value refiners. I know of a codeplex project with multi-value refiners but haven't tested it, but you might want to give it a shot. In short it splits the string, eg. red;yellow;blue, and look at it as seperate values. I can't see why this shouldn't work for BCS fields either. Here is a description of how to ...


1

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


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

Refinement occurs AFTER the query. What you are attempting is more like the Advanced Search offered in SharePoint. The end user can select a link for "Advanced Search" and be taken to Advanced.aspx in the search center. The Advanced Search page contains a web part that you can alter to meet your needs. I would start with that to see if you can get your ...


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

Yes, It is read only property and I couldn't update it with PowerShell too. I can't imagine any adverse affects of creating a new content source and removing the default one.


1

You can't, but you can create new Content Sources and remove the start addresses from the original.


1

AFAIK there is no out of the box solution for this. But with this solution and adjusted refiners you can get what you want: http://sprefiner.codeplex.com/


1

Based on my knowledge you could do that in someway. I found a post of Mastykarz where I explain how get the list of terms by js. Using this you should be able to do a search query: http://blog.mastykarz.nl/building-global-navigation-sharepoint-2013/ Another good point of view is this tool: http://sp2013searchtool.codeplex.com/ it could help you to ...


1

The way I understand Result Sources, they are the new Search Scopes. It's more a renaming thing, though there are subtle differences. You may be mixing terms here. You wouldn't normally use a scope as a refiner, but perhaps have different results pages for different scopes, as you'll probably want the presentation of the results to vary.


1

How about: directoryPath = directoryPath.substring(0, directoryPath.length -1) + '*' refiner = { "Path": ['starts-with("' + directoryPath + '")'] }; It could be a trailing / that stops it from including the current site


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


1

Okay here is what I implemented at the end. Add a Search Box webpart in that page. This webpart can be connected to the content search webpart, using webpart properties. Hide this webpart using CSS. Now in the content search webpart , edit the webpart properties and edit the query to accept data from the Search Box. On change event of dropdownlist , dump ...



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