List Columns not available as an option for crawled property

Question

We are operating on SharePoint 365 and I am trying to configure a custom search query. To this effect, I'd like to map a managed property (i.e. refinablestring05) to a column in a list. However, when editing the properties for a managed property, the column I'd like to reference is not showing up. In fact, none of the list columns are showing up.

I have reindexed the list, the site (which is a sub site) and the parent site. I have ensured that SharePoint Server functions are active (both at the parent site and sub site). I have also confirmed that the list and the site are set to searchable and available.

I have also confirmed that the columns in the list contain data. I have waited 15, 30min, 1 hour and even 24 hours for the site to be reindexed and crawled, but still these columns are not appearing.

What am I missing? Hopefully this is enough information to suggest some points to troubleshoot. Thanks!

Answer 1

At this time it appears my issues might be due to SP148979 - Issues with search schema settings. According to MS a fix should be coming out October 19th. Will try my implementation at that time and hope that corrects my problem.

Answer 2

Columns, depending on how they are created are not inherently searchable. If the person creating them just used the "+" sign to add them, that would be your problem. Columns should be created by clicking on the Ribbon under Library or List, then clicking create column. I would recommend creating a sample column this way, inputting some test data, and then running your search against the new column.

I unfortunately do not know of an easy way to move the data input into all the bad columns into new good columns. Nor do I know of a way to make the bad columns good. But at least the root issue should be known. While tedious, if you use the edit items functionality you should be able to at least copy paste from the data in the bad columns' cells into the good columns' cells.

Good luck!

More info here: Info from ShareGate

Answer 3

Is your field a Site Column? Because a custom field must be a Site Column to use it as a Crawled property. You can see a good example here