none
Bug: Crawled Property name is case sensitive and display name is worng RRS feed

  • General discussion

  • Hi everyone,

    I've encountered something very annoying:

    Let's say I have a crawled property named "level". When using Admin UI, I can see it is named "level". When using powershell I can see it's named "level". When I'm trying to pass it to a pipeline extension, it simply doesn't get caught.

    I took a look at the spy, and saw that it is named LEVEL, with capital letters. In the pipelineextensability XML file, I capitalized the letters - and voila - it worked !

    It's not new to me that pipeline extensions are case sensitive, but it's new to me that you can't trust the displayed name.

    Amir

    Sunday, April 8, 2012 8:10 AM

All replies

  • Hi,

    This is "known", and using either FFDDumper or Spy to check the casing inside the pipeline is extremely useful. But I agree, it would work equally well with case insensitive crawled property names in my opinion. I have seen the upper casing on all <meta> tags in HTML. What kind of crawled property did you see this on? 

    I suspect the display names stored in SharePoint to be lower cased.

    -mikael


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/

    Sunday, April 8, 2012 6:32 PM
  • Hi,

    Same here.. <meta> tags in HTML :)

    Amir

    Monday, April 9, 2012 6:38 AM
  • Hi,

    And meta tags for some reason are always upper case inside the pipeline :)

    -m


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/

    Monday, April 9, 2012 4:47 PM