Refinement Panel - Custom Range

Question

Hi,

I've been trying to configure a range refiner based on an integer managed property but I got no luck so far. This is the only reference I could find on MSDN (http://msdn.microsoft.com/en-us/library/ff625183(v=office.14).aspx). There's also this post where it its pretty close to what I need (http://todd-carter.com/?tag=/SharePoint+2010;+Search;+Refiners). Here is the XML I'm using (just an extract):

  <Category
      Title="Annualized Sales"
      Description="Annualized sale of the retailer"
      Type="Microsoft.Office.Server.Search.WebControls.ManagedPropertyFilterGenerator"
      MetadataThreshold="1"
      NumberOfFiltersToDisplay="3"
      SortBy="Custom"
      ShowMoreLink="False"
      MappedProperty="annualizedsales"
      ShowCounts="Count" >
    <CustomFilters MappingType="RangeMapping" DataType="Numeric" ValueReference="Absolute" ShowAllInMore="False">
      <CustomFilter CustomValue="less than 100K">
        <OriginalValue>..100000</OriginalValue>
      </CustomFilter>
      <CustomFilter CustomValue="100K - 200K">
        <OriginalValue>100000..200000</OriginalValue>
      </CustomFilter>
      <CustomFilter CustomValue="more than 200K">
        <OriginalValue>200000..</OriginalValue>
      </CustomFilter>
    </CustomFilters>
  </Category>

The managed property is configured as a refiner and the filter works if I use annualizedsales:<=100000, but I cannot get it to show up at the Refinement Panel (non range refiners work fine)

Thanks!

Answer 1

I am having exactly the same problem. Part of XML that specifies ranges seems to be ignored completely. Instead I get ranges that are generated automatically and I have no control over it.

Did anyone managed to solve this?

Answer 2

There is a checkbox that says "Use Default Configuration", uncheck that. then your xml configuration will take effect

Answer 3

Unfortunately not, not even the guys from MSFT/FAST were able to figure it out. It was just a proof of concept, so we moved on without it.

Answer 4

Thanks Todd, but that's not it (at least not in my case). Regular refiners work fine, the problem is only with range refiners. We've engaged with MSFT support but they were not able to resolve it yet. 

Answer 5

I'm totally confused, this worked perfectly for me with the xml you provided at the top. Can you look at this image and tell me if this is what you're going for?

http://farm5.static.flickr.com/4055/4646583108_4c11481b42_b.jpg

I have a video of me creating it but skydrive is down right now.

Answer 6

Yep, that's exactly what I was hopping to see, but I got nothing over here. The extra steps I've taken were mapping the crawled property as a managed property (deep refiner) and making sure the values were available in the results (and they were). Do you recall any extra steps to get it working like that?

Answer 7

http://qmiz3g.blu.livefilestore.com/y1pd1Jpv2Izq89aPB13ZrMatkqnG73GKG3_vi-qO5zhhBehA6DdvluPwFL3P54MQH2n4GMCtDFVwT1T74GPAynBOPKoL4zQYAKV/Range%20Refiner.wmv?download

Its more blurry than I would have liked but heres what I did

1. Made list and added AnnualizedSales column as integer
2. Added Item 1, Item 2, and Item 3 with sales 50,000 150,000 250,000
3. Crawled so it knows about the crawled property
4. Added managed property and associated with crawled property
5. Make new search site
6. Edit the refiner panel on the search results page of the search site. Uncheck the use default configuration and add your category XML to the categories (both under Refinement).
7. Do another full crawl.

Answer 8

The problem here is most likely that you first CustomFilter tag.

The value ..100000 results in Fast defining a bucket in the range of -2147483648 and 100000. It seems that SharePoint can't handle this value.

If you change it to 0..100000, it hopefully will work. I haven't had any problems with any upper limit.

Answer 9

Would it work if you assigned ValueReference to "Relative"? Your non-range refiners are working because they have an absolute ("Absolute") value reference. All ranges must be set to ValueReference="Relative".