SharePoint etc.

I have got an interesting issue with Document Set content type in SharePoint 2010. Document Set content type. Below are the actions I have taken: 1. Activated Document Sets feature on the Site Collection level 2. Created a Document Library 3. Set Allow management of content types to "Yes" 4. Added Document Set to that Document Library from existing content types 5. When I try to create new document with the content type Document Set I'm getting the following error: "One or more field types are not installed properly. Go to the list settings page to delete these fields". I have posted a question on SharePoint Developer Center to resolve that: Document Set content type issue UPD: There was a Beta version bug. I published a new post about Document Sets recently to start illustrating how it works. It's here: Document Sets - SharePoint 2010 - Part 1

I have run into some issues with SharePoint 2010 and have come across the helpful link: Troubleshooting your SharePoint 2010 Errors

I have started playing around with SharePoint 2010 Beta recently. One of the most attractive features of the new version is Managed Metadata. It allows people to maintain metadata across the site collections. Here's the quick sample of how you can use managed metadata in SharePoint 2010. Scenario We have a list or library to store Customer Sales Orders. This list is located on several site collections. Our goal is to manage metadata for those lists centrally. I have two site collections: wylde.slava.com and solutions.slava.com. Step 1. Create a custom list called Customer Sales Orders on both site collections. Step 2. Add a managed metadata column called Sales Order Status on solutions.slava.com: Select "Customize your term set" option to create new term set called Sales Order Status. Then it appears in the list of available term sets to use anywhere else. Select this custom term set. Step 3. I have done the same for wylde.slava.com, but when I created a...

Programmatically Adding to and Removing from a Person or Group Column

I have found a quick reference guide for MOSS 2007 end users aka information workers. It's here: MOSS 2007 Quick Reference Card

I'm at the SharePoint Conference in Las Vegas right now. SharePoint 2010 is a great thing! Even from the first sight it's a huge amount of effort invested in enhancement from 2007 version. It also has a lot of new features. Will post more on that later. Stay tuned.

Situation There is a MOSS 2007 farm with Shared Service provider configured to use mysites.domain.com as a My Sites host Web site. Two Alternate Access Mappings were created for My Sites Web site: Default Zone: http://mysites.domain.com Extranet Zone: https://mysites.domain.com In IIS this is a single Web site with aditional binding for https on port 443. If you search for people using Extranet Zone mapping for the SharePoint Web site in the search result the URL is https://mysites.domain.com: After installation of Infrastructure Update for Microsoft Office Servers search result Web site URL for people looks like https://mysites.domain.com:80 which is wrong, because there is no Web site on port 80 available using https: Some ideas are explained in the following article: People Search Results adds a :80 Suffix to results on an External Facing Site And cosmetic workaround is provided in the following article: How to remove something (the port) from the URL as returned in the search resu...