A customer reported this problem to us and it was quite a learning to know how content processing works in SharePoint 2013 with respect to crawled properties from a custom XML indexing connector. Thought this could be worth sharing! So, here’s the problem. Follow the steps outlined in this blog post Create a custom XML indexing connector for SharePoint 2013 and perform a full crawl of the custom XML connector content source. Go to Search Administration > Search Schema > Categories...(read more)![]()
↧