This purpose of this article is to look at how SharePoint 2010 and SharePoint 2013 Search can automatically create new managed properties when end-users create new metadata columns in their libraries and content types. So if you’re reading this, I assume you must already know a bit about SharePoint Search, how to configure your Search Service Application and a bit about Crawled Properties and Managed Properties. However, I’ll provide little background info first…
Crawled and Managed Properties
Crawled properties are metadata (such as InvoiceNumber, VendorId, or OrderDate) that are extracted from documents and SharePoint columns when the Search service performs a crawl. However, crawled properties are the internal representation of this metadata. To enable users to search on this metadata, we need to create managed properties that are mapped to the crawled properties.
Now there’s lots of great background documentation from Microsoft on Crawled and Manage ...
Read More
Recently, I encountered a frustrating experience upgrading a custom web part on SharePoint 2010 farm.
In my case, the farm has two Web Front End servers (not load balanced), let’s call them WFE1 and WFE2. I needed to upgrade my web part from version 3.0 to 3.1. So I ran PowerShell’s Update-SPSolution command on WFE1 to update the solution containing my web part. After running the PowerShell command, I logged onto a site using the URL for WFE1 and confirmed that my web part was updated to v3.1, but when I did the same from WFE2, I found my web part was still using v3.0.
Looking in the Solutions Management page from Central Admin, I found my that my solution was still listed as “Scheduled For Deployment”, so I waited a bit to see if perhaps some timer jobs just hadn’t fired off yet. After 15 minutes or so, the solution was still scheduled for deployment, and at this point I determined that the issue needed some troubleshooting.
Initially, I assumed the ...
Read More
Getting ready for Microsoft’s SharePoint Conference 2012 next month, I’ve been testing out the new App Dev model in SharePoint 2013 for the last few weeks. But tonight, I decided to start digging into the out of the box features of SharePoint 2013 and comparing them to SharePoint 2010.
I decided to focus on the wiki page editing features, since this was one aspect of SharePoint 2010 that was universally disliked by every SharePoint user I know. My hope is that Microsoft will greatly improve the wiki editing functionality in SP2013. Thankfully, I have found some critical improvements within the wiki editing experience. Although, I have not yet completed an exhaustive analysis of the wikis in SharePoint 2013, this article will focus on one major improvement that I noticed right away.
One Major Problem with Wikis in SP2010…
On numerous occasions, I’ve found content residing in some MS Word document, that I need to post into a SharePoint wiki page.& ...
Read More
This blog post is based on a white paper that I authored last year after assisting my team with a few SharePoint 2010 upgrades. For some reason, I forgot to post this last year, and just came across this document again, so I decided to post it now. I realize that many organizations have already completed upgrades to SharePoint 2010. However, many companies are still running on MOSS (or even SharePoint 2003) and planning an upgrade to SharePoint 2010, so I believe this information will be helpful to some you. SharePoint is really not a “product”, but rather a sophisticated platform for building and hosting a variety of complex business applications. This makes SharePoint a powerful and flexible system that organizations rely upon as a mission-critical part of their IT infrastructure. It also makes the process of upgrading an existing MOSS or WSS farm to SharePoint 2010 more complex than most applications or other server products from Microsoft. Purpose The purpose of this ...
Read More
Today I decided that I needed to change the Item-Level Permissions settings for a document library so that users could only read the items that they had created. For SharePoint lists, the Item-Level Permissions setting is easily configured under the list’s Advanced Settings section, like this: However, when I went to the Advanced Settings section for my document library, there was no section for Item-Level Permissions. I checked a few other lists and document libraries and confirmed that apparently most list types support this configuration, except for document libraries! So my next question was whether Item-Level Permissions settings could not be changed in a document library at all, or whether these options were simply not displayed in the browser for the Advanced Settings in a library. I figured the easiest way to determine this would be to attempt it with PowerShell in a test environment… if it was not supported, the PowerShell commands would simply fail to execute ...
Read More
If you wish to utilize Ratings on a SharePoint list or library, you might think that you can do so by simply adding the “Rating (0-5)” site column to your existing list, library or content type. In fact, SharePoint will allow you to do that, however doing so may or may not provide the intended results.
Read More
I recently solved a seemingly obscure problem configuring SQL Server Report Services (SSRS) 2008 R2 using SharePoint Integrated Mode. However, perhaps this problem isn't as obscure as it seems and maybe this article will help others.
Read More
On September 18th 2010, a few members from the San Diego SharePoint Users Group (Tony Rockwell, Chris Givens and Galen Keene) and I trekked to the Hilton Los Angeles Airport for SharePoint Saturday LA.
Read More
I found a minor issue today when trying to retract a simple, custom solution from a new SharePoint 2010 test server.
Read More
Today, a co-worker created a custom web part for me in C# and packaged it as a solution (.wsp file) for deployment on my local test server. The deployment steps for this solution included a simple STSADM script to assist in the deployment. However, since I have not played around with PowerShell much yet, I decided to translate this STSADM script into PowerShell and use that instead.
Read More