tips & tricks
Working with Managed Properties in Search-driven publishing scenarios
SharePoint 2013 does great job configuring things for you in search-driven publishing scenarios but there are a few things you should keep in mind to save yourself trouble.
Inconvenient Content Targeting with User Segments in Search REST API
Content Targeting with User Segments just works with Content Search Web Parts but some additional work is needed if you want to leverage it with the Search REST API.
Debugging setting properties in anonymous Search REST queries
Leveraging SharePoint 2013 Search REST API for anonymous users allows you to build powerful search-driven solutions. Often, particularly in the early stages of the project, queries might not work as expected. So how do you find out what’s wrong?
Debugging content recommendations in SharePoint 2013
Content recommendations in SharePoint 2013 are a powerful mechanism that can help you expand the reach of your content and increase the conversion from your website. The process of gathering and calculating recommendations is quite complex and consists of quite a few moving parts. If, for some reason, you’re not getting any recommendations there are a few things that you can check to verify that things work as expected.
Inconvenient getting a specific item using SharePoint 2013 Search
SharePoint 2013 Search contains rich capabilities that help you find the relevant content. What if however you already know what you are looking for and just want to get a link to it?