Hi all,
I have created a farm solution (for SP 2013 on prom) in Visual Studio 2012 (with whole bunch of site columns, content types, lists, libraries … – all declarative with element.xml files) and deployed to my client’s environment. Everything looks Ok, however, the Crawled & Managed properties related to my custom site columns are not generate as part of crawling the content! The search service is created, the site is fully crawled, and also there are enough content in the site to trigger the crawler to generate the managed properties. However, for some weird reasons, the Crawled & Managed properties aren’t being fully generated!! (Some site columns do have both managed property and crawled property, but not all of them!)
Anyone had the same/similar issue before? Appreciate any help or suggestions. J
Cheers,
Hi,
SourceID is the solution for this problem!!!
Make Sure that you have StaticName and SourceID defined in your field definition XML before you deploy your farm solution into your farm.
If you discovered this issue after you have deployed your solution to your farm and are wondering why no crawle properties shows up in search schema I would recomend follow this steps:
1. change the sourceid property in your field definition xml
2. redeploy your solution into your farm
after you have added your site column to a list this change wont get to the field definition at list level and the crawl behavior will be still bad.
3. To solve the problem update the SchemaXML property of your Column at the list level. Replace the GUID like SourceID with “‘http://schemas.microsoft.com/sharepoint/v3″
$list.Fields[“Farm Col 2 Root”].SchemaXML = “”
$list.Fields[“Farm Col 2 Root”].Update()
run the fullcrawl after you’ve updated your field at the sitcollection level and at the list level and everything will work as expected.
