SharePoint 2010 - Indexing a Calculated Column to use as List Filter

Question

Hi there,

I've struggled to find much information on this, but I am looking to Index one of the Calculated Columns I have in a list, so that I can use it to filter a List View.  This has all come about because I have reached the List Threshold (5000 items) and instead of changing the List Threshold I want to find a more proactive fix.

I found this question here ( http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/21ec1ed2-e8a9-4506-932e-d054f2defb2c/ ) which says to add the column as a Search Metadata Property, which I have done, but the Column still does not show up in the drop down list when I try to choose it as an Indexed Column for the list.

Any help would be greatly appreciated.

Thanks,

EDIT - Sorry, I've just realised this is in the wrong area to ask the question but am unsure how to move

Answer 1

Hi Brett,

Long time! Did you ever get your calculated column into your search index? After you added it as a Metadata Property did you kick off a full crawl on the content source it's a part of? Once that's done, return to the Metadata Properties page (under 'Queries and Results' in your Search Service page) and click on 'Crawled Properties'. Enter the name of your property in the search box at the top to find it. Click on the name of the metadata property and you should see urls in the 'Content using this property' sample documents. While you're there be sure that the checkbox 'Include values for this property in the search index' is checked and that the field has a mapping to a managed property. It can be tricky to get the search results you're after!!

---

Love them all...regardless. - Buddha

Answer 2

Thanks for the reply, better late than never!

Double checked all the information you have mentioned.  Everything is set up exactly the same.  The same URLs are going to the right area, it is definitely mapped to a managed property.

Still sourcing a fix on this one..

Answer 3

Hi Brett,

Even longer time but think you'll find indexing calculated columns isn't supported.