-
Inconvenient programmatically working with Managed Navigation and anonymous users
SharePoint 2013 offers rich API for interacting with Managed Navigation. Unfortunately, some additional work is required if you need to use it with anonymous users.
-
Granting the “Retrieve People Data for Search Crawlers” administration permission on the User Profile Service Application using PowerShell
When working with search-driven solutions, or even if you just want to be able to search for people, SharePoint Search has to be granted access to that information in order to crawl it. Generally all of this is being automatically taken care of when provisioning the Search Service Application. On rare occasions you might however need to grant this permission manually.
-
Inconvenient copying Host Named Site Collections with multiple SPSiteUrls
Copying Site Collections in SharePoint 2013 is trivial, except if you are trying to copy a Host Named Site Collection with multiple SPSiteUrls.
-
Inconvenient Managed Properties: when strings are numbers
Recently I wrote a blog post on how standard Managed Properties are not enough for supporting particular scenarios. For example, when building content aggregations sorted on dates or numbers you would need a custom Managed Property. The reason for that is the fact that, although there are some Refinable and Sortable Managed Properties available out of the box with SharePoint, despite the type communicated in Search Schema, they return string data which makes them useless for sorting on numbers.
-
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.