1

I have content type on my site with 3 custom columns defined:

  • "Corporate sponsored" - Single line of text column
  • "Country" - Yes/No column
  • "Customer Name" - Managed metadata column

This content type is used in my custom list. Now, I want to use SharePoint Search API to fetch items from this list. I use "SharePoint 2013 Search Query Tool V2" from Codeplex to test search API.

I encounter some problems with crawling/indexing my columns:

  • Yes/No column was successfully crawled, and managed property "CorporatesponsoredOWSBOOL" was created. It also returned by Search API. This field is OK.
  • Managed metadata column was crawled, and managed property "owstaxIdCountry" was created. But when I try to fetch it's value using Search API, this field does not appear in search results at all.
  • Single line of text column was not crawled, no managed property was created. It also does not appear in search results.

I use SharePoint 2013 Online developer trial subscription.

My search query looks like this: 

~/_api/search/query?querytext='edu'&selectproperties='CorporatesponsoredOWSBOOL%2cowstaxIdCountry%2cCountry%2cCustomerName%2cCustomer_x0020_Name%2cTitle'
Improve this question
6
  • You can always create a Managed property yourself, mapped to the crawled property created when SharePoint first indexes content in your custom columns: blogs.technet.com/b/tothesharepoint/archive/2013/03/06/… Commented May 16, 2014 at 13:13
  • @RobertLindgren, the problem that crawled property was not created for text column. Commented May 16, 2014 at 14:09
  • Make sure you have added content to one of the items in that specific text column, then do a full crawl Commented May 16, 2014 at 14:10
  • @RobertLindgren, yep, there are data in all custom columns. I cannot find where i can manage full crawl schedule in my SharePoint Online tenant. I can only schedule my list to be reindexed. Commented May 16, 2014 at 14:30
  • Ah, if it is in Online all you can do is patiently wait I'm afraid Commented May 16, 2014 at 14:31

1 Answer 1

Reset to default
2

I had encountered a similar situation but managed to solve it by creating new managed property for each of the fields and mapping the custom fields to the respective new managed properties.

Hope this helps.

Kind regards,

SK

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.