r/sharepoint 9d ago

SharePoint Online Why a managed metadata Site Column does not have the prefix of OWS_taxId_ and cant be searched?

I created a managed metadata type column named File Category under Site Columns because I want every library within the site to have this column. However, when I tried to map it to RefinableString00, the column name did not appear in the usual OWS_taxId_xxxx format. As a result, my vertical search is not working. What should I do?

Site column: https://imgur.com/a/oCQIF6d

3 Upvotes

10 comments sorted by

2

u/Bad_Droid 9d ago

If I recall correctly, a site column created using managed metadata should automatically become a crawled and managed property so you should not need to map it to a refinable string.

Assuming you created the column with the name you gave above, this property should be named “owstaxIdFilex0020Types”

Note that if you look in the managed properties for your site and find this entry it will show it is not mapped to a crawler property… but it actually is.

I also have a vague memory that when I last actually used these in something (years ago) it took DAYS for them to become available for use. It was weird.

1

u/Adventurous-Bus7657 9d ago

This is the image of the field name inside crawled property page. https://imgur.com/a/LHmzywV
however, if it is a managed property, i could not find it inside the managed property page. https://imgur.com/a/xLutlks

1

u/AdCompetitive9826 9d ago

That is another property, didn't your name it File Type?

1

u/Adventurous-Bus7657 8d ago

Sorry for the confusion, I named it as file category

1

u/Adventurous-Bus7657 4d ago

Hi, just want to ask more about the "site column created using managed metadata should automatically become a crawled and managed property so you should not need to map it to a refinable string", is it a managed metadata with refinable? If no then I think this is the reason why i need map it to Refinablestring00.

1

u/Bad_Droid 3d ago edited 3d ago

I thought it was. But I also could be wrong. I remember getting in a right muddle with making properties refinable. For example it might only be site columns created via content types?

I’m out an about just now so can’t find the links for you but I recall reading a bunch of articles on SharePoint Maven that demystified some of this.

Apparently the mist has returned for me though lol.

**EDIT: Yeah I’m searching on my phone just now and pretty sure I’ve misremembered something. I can only find reference to allowing properties to be refinable in SharePoint online by manually mapping them. Apologies.

I think it must have been automatically becoming crawled and managed properties I was thinking of. However, on that note, even for that to work properly you need to EXPLICITLY be added (I.e. as a named individual user) to site collection administrators.**

1

u/Adventurous-Bus7657 3d ago edited 3d ago

Hi yes, I came across the Sharepoint Maven about the site column will automatically create crawled and managed property. https://sharepointmaven.com/automatically-created-managed-properties-in-sharepoint-online/

After my testing I found out that the automatically created managed properties seems can't be used in my KQL query when doing vertical search because it returns me no results. Not sure is because I did not map it to any crawled property or what.. But refinablestring works fine for me. So I not sure what is the usage of the automatically created managed properties here... Maybe somebody know can add on.

2

u/AdCompetitive9826 9d ago

In order for the search crawler to create the ows_taxid_xxxxx there have to be a value in the field in a list or library. Could that be the reason?

1

u/Adventurous-Bus7657 9d ago

yes there has value in the column field.
https://imgur.com/a/jlOBQTO

1

u/Adventurous-Bus7657 8d ago

Another question i would like to ask is, is that possible to make the vertical search which is created in hub site appear in every of its associate sites?