0

I have yet to find a definitive answer to this question. Right now this does not work for me in sharepoint 2007 and the only common characteristic I can find for the fields is that they are calculated fields.

A full crawl has been performed and the calculated fields show up. Managed properties have been added and the advanced search web parts properly modified to allow search on the properties. All other (non-calculated) fields added to the managed properties and search work fine.

The Calculated fields are text fields with the formula "=LEFT([field name],2)". The reference field is a choice field.

Anyone? If search on calculated fields is not supported, I really just need to get back to the user to say "Nope, it can't be done."

Improve this question

1 Answer 1

Reset to default
0

So this won't be 100% helpful, but my view is that is can be searched, at least, it can be searched in FAST4SharePoint.

In the FFDDumper log (a FAST4SharePoint tool) I get the following row (my calc column is [Title] & "HIHI"

50 00130329-0000-0130-C000-000000131346:ows_CalCol:31 s48 string;#COMPETETIVE ANALYSIS HIHI

This content is first crawled by the SharePoint crawler and then processed by FAST. If SharePoint didn't crawl it then FAST wouldn't see it. I don't have standard SharePoint search setup, but logically the content should be searchable as it's not highly complex.

Do me a favour and try searching for "string;#". The "string;#" is not there for any of my other text field and is only visible in my calculated column. It might be that SharePoint isn't actually smart enough to deal with this and doing an exact match based on this might yield a search result.

Whether or not this is usable for your client is another question entirely.

Improve this answer
5
  • Oops, I should have specified that this is SP 2007. I'll edit the question to ask it properly.
    – user2716
    Mar 29, 2011 at 20:50
  • So Peter, I figured you probably didn't have FAST. Could you try looking for the entire string (i.e. "string;#My CalculatedText"). I'm thinking your index might be storing similar data.
    – Neil Richards
    Mar 29, 2011 at 22:12
  • Ok, you officially get my "Most brilliant person in the world" award for today. (It is highly prestigious :)) The search for that worked and brought back the expected results. Thanks for the answer! Now I need to figure out how I can make OOTB advanced search work for that.
    – user2716
    Mar 30, 2011 at 14:46
  • Checkout sharepoint-insight.com/2008/10/05/… apparently >> "The solution is, just go back and edit your managed property mapping and instead of mapping Category; map ows_Category. This is an internal property generated by the Sharepoint when you created Category and this property saves the actual value."
    – Neil Richards
    Mar 30, 2011 at 16:15
  • Actually, I am already mappingthe ows_ version of the column, which is the only one that I can find in the crawled properties.
    – user2716
    Mar 30, 2011 at 17:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.