SharePoint Search 2013 return values

chuck Traywick 96 Reputation points

Some of the values to which managed properties are attached, when returned adds string;# to the front of the value. Example, have a date field that has a calculated column that extracts the month as a string. We crawl that as anniversary. When we use that in a refiner as shows string;#03 for example instead of 03.

What settings cause this?

Thank you

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,215 questions
0 comments No comments
{count} votes

Accepted answer
  1. chuck Traywick 96 Reputation points

    Wonder if this is due to the fact that those fields are calculated? We extract part of another field into a calculated field.

    Could that be it?

    Thank you

4 additional answers

Sort by: Most helpful
  1. Allen Xu_MSFT 13,776 Reputation points

    Hi @chuck Traywick

    I could also reproduce this issue on my end.

    As per my research, this issue seems to be by default and I didn't find any OOB settings can fix this issue. I would suggest open a ticket with Microsoft to confirm on this scenario.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. chuck Traywick 96 Reputation points

    Hi Alex:

    Thank you for the prompt response. What we are having is the prepend of spring;# on the front of the returned value. See below:


    On some string values the word string;# is added to the front of the value as the image shows.

    Thank you

  3. chuck Traywick 96 Reputation points

    OK, will try that. Users are about to start so will have to wait till tonight to test. But yes, in some values string;# is added to the front.

    Thank you


  4. sadomovalex 3,626 Reputation points

    did you try to reset search index and perform full crawl after that? (if it is possible it your case of course)

    0 comments No comments