This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 96%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECT%3C/text%3E%3C/svg%3E)
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
Chuck
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
Chuck
Yes. I tested other column type like signle of text, it works normally.
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.
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
Chuck
Thanks for your reply. So, you mean that your search results are displayed as "string;#xx"? I'm trying this: edit the calculated column to let it retrun number type instead of text type values and map it to a managed property with interger type. Not sure if it will help. I will get back to you if there is any update.
Could you kindly share your SharePoint build version or the CU deployed to your farm so that I can configure an environment to have a try to reproduce such issue on my end?
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
Chuck
I have tried to set both calculated column return type to number and managed property to interger type but nothing makes a difference unfortunatelly. Suggest you open a ticket with Microsoft to check if it is a bug or something is going wrong.
did you try to reset search index and perform full crawl after that? (if it is possible it your case of course)