Corey Roth [MVP] : Office 365 Grid, SharePoint Online, Enterprise Search

Importing Search Configurations with SharePoint Apps

CoreyRoth — Wed, 03 Apr 2013 16:21:44 GMT

The Office Developer Tools team snuck a new feature into the RTM version of the tools for Visual Studio 2012. This new feature allows you to deploy apps and actually alter the search schema on the host web. That’s right. You can deploy an app and it will directly change the search configuration on the host. They just released documentation on it a while back, but as usual, I wanted to share my experiences. That and I know you all like screenshots.

What does this feature actually do? Well let’s back up a bit. If you remember back from my post, Search is Everywhere, I mentioned the we now had the ability to export and import search settings. This works at the SSA, site collection, and site level and allows you to move everything from result sources to managed properties from one environment to another. This is big as it lets you finally promote search settings between environments and maintain a true SDLC when it comes to search. Why do we care about search configuration with apps? Well this allows the developer to package up search settings in Visual Studio 2012 and then move them to production without having to do manual steps or use PowerShell. This also means you could include search settings in an app that you would put in the Office Store. It certainly opens up possibilities.

To test this out, go to your source site collection and customize your search settings. In my example, I created a custom result source and some managed properties on our source site. In my example, I actually did this on an on-premises installation of SharePoint 2013.

This particular result source does nothing exciting. It simply limits the search to documents, but it serves as a good example. I’ve also created a managed property mapped to the Author crawled property. You may already know about this part, but I am showing it for a reason.

Now, I am going to export my search settings of my site collection, by going to Site Settings –> Search –> Configuration Export.

At this point, I could manually import the search settings using Configuration Import on another site collection. However, we want to do this from an app. Let’s get started in Visual Studio 2012. Start by creating a new SharePoint-hosted app. Once it is created, add an item to the project and choose Search Configuration.

The next step will ask for the path to your configuration XML file that you exported.

At this point the process is done. It will show you an XML editor with the contents of your search configuration. According to the MSDN documentation, you then need to edit it and set the DeployToParent element to true.

We then need to grant permissions to access the Site Collection. To do this, open AppManifest.xml and then click on Permissions. On this tab, add a scope of Site Collection and set the value to Full Control.

At this point, we are are ready to deploy. In my example, I am taking my search configuration and deploying it to an Office 365 SharePoint Online tenant. When the app deployment completes, you’ll be prompted if you want to trust the app. Trust it and then you should see your app start page.

At this point, you are just going to see you default app start page. There is nothing visible in the application. Go to the Developer Site (or the site collection you deployed to) and go to the Site Settings. Then look at the Result Sources. If everything worked correctly, you should now see your new result source there.

It was successfully deployed. Now what about the managed property? Unfortunately, it is no where to be found. If you go back to Visual Studio and look at your XML, you’ll notice that your managed property definition is no where to be found there either. If you check the source file before you imported it though, you’ll see the definition. After I noticed this particular behavior, I reached out on Twitter and @chakkaradeep reached out to me and told me that managed properties aren’t supported in this deployment model. That made me kind of sad because that’s what I want to deploy the most. I’m sure there is a technical reason though that he’ll explain to me sometime though. You can still deploy managed properties via Configuration Import though which is still a great added feature of SharePoint 2013.

You might be curious if the result source is removed when you uninstall the app. It turns out that the changes are indeed removed when you uninstall.

Aside from the managed properties not being available, this is still a pretty cool feature and it has me thinking about some new things I can do that I didn’t think were possible before. I’m pretty excited to work with it more.

Determining the most popular items in a document library in SharePoint 2013

CoreyRoth — Thu, 28 Mar 2013 19:39:39 GMT

With the combination of analytics and search in SharePoint 2013, there is a heap of new features to help determine which content is actually being used. No longer is this information buried in reports for administrators, but it in fact is available right from the ribbon in a document library. Maybe you have even noticed the Most Popular Items button in the ribbon already. You can find it on the library tab in the middle.

Click on it and you will be taken to a custom search results screen that shows you recent views and total views.

What’s nice is that you can even search and refine within the report if you are looking for something specific. You can also click on the Popularity Trends link to get a nice graph of the usage of the file over time.

Behind the scenes, this report is powered by the Popular result source. You can also use this source to look for popular items across your entire index. As a developer, the possibilities are quite interesting.

My particular tenant doesn’t have a ton of usage, but if you’re already running SharePoint 2013 you might be able to extract some valuable insights from this report. Try it out today.

Speaking at Office 365 Saturday Redmond!

CoreyRoth — Wed, 22 Feb 2012 21:45:29 GMT

I’m excited to be speaking at the first Office 365 Saturday in Redmond on 2/25. This new event will be an exciting display of all things Office 365. I’ll be talking about all of the cool things you can do with Search in SharePoint Online. I gave this talk at SPC11, but I gave the talk an upgrade with the use of Visual Studio 11 Developer Preview. We’ll look at what you can do out-of-the-box with search and then write a custom Silverlight application to query search web services. If you’re looking to get more out of search be sure to stop by and check out my session.

How to: Query sites and site collections using SharePoint Search

CoreyRoth — Fri, 13 Jan 2012 19:41:21 GMT

I often refer to my Handy Keywords in SharePoint Search because it forms the building blocks you need to become a rock star at writing SharePoint keyword queries. Today, I want to expand upon that post on how you can use search to return a list of sites or site collections. This is useful when you want to quickly inspect a SharePoint farm using the Search Center. The secret behind returning sites with Search is use of the contentclass managed property. You just have to know what value to specify. To return a list of all sites in the search index, we specify a value of STS_Web (remember our translation guide). Here is what it looks like.

contentclass:"STS_Web"

This works pretty well. However, if you inspect the results on your own server, you might quickly notice one thing missing. The root web of all the site collections is not present in the search results. To get the site collections, we specify STS_Site instead.

contentclass:"STS_Site"

Notice, I now have all of the site collections on my particular tenant. If you want the results combined, you simply combine the queries.

contentclass:"STS_Site" contentclass:"STS_Web"

Now you might be thinking this is great, but you don’t want every site and site collection on the farm. You want to restrict it to a particular web application. That’s actually pretty easy, just refer back to the handy keywords post and use the Site managed property. In my case, I’ll restrict the URL to my main web application.

contentclass:"STS_Site" contentclass:"STS_Web" site:https://dotnetmafia.sharepoint.com

There are lots of ways to get lists of sites in SharePoint, but I find this one works well since it doesn’t require a line of code for you to try. Of course, as a developer, you can make use of this with the KeywordQuery class inside your own application. This works with SharePoint on-premises as well as SharePoint Online. All screenshots were from my personal SPO site.