Migrating file shares to SharePoint 2010 requires a lot of activities around Information Architecture to design the taxonomy according the business needs and provide rich content usability, but apart of this a large portion of file migration engagement takes the actual migration process. Migrating files to SharePoint is very time consuming process, due to the nature of SharePoint to store all content in Content Database. Therefore, all files that are published to SharePoint sho...

  SharePoint 2010 introduced a new feature "Content Organizer" to organize your content automatically, based on custom-defined rules. However, these rules add new entity to the hierarchy of events that can be executed for the List items, and this execution order is not well documented. It's important to understand the sequence to process documents accordingly. For example, when the user uploads his CV to the library you want to add watermark by Workflow, update .docx metadata with event r...

Workflow in SharePoint 2010 will always run as a service account (typically the IIS Application Pool account) and is only supported when using Secure Store Service (SSS) or RevertToSelf (which is turned off by default due to security implications). This limitation is designed to protect SharePoint 2010 from malicious models/developers. Because access to the backend will always be initiated as one account, you will lose track of who is making the changes. To work around this, you can have...

SharePoint 2010 provides the better performance for the List, however some limitations still have place: Maximum number of List Items is 50 million Constrains that block Lists: Max of 8kb of data per list item (not including attachments) Max of six projected fields allowed on joins

SharePoint 2010 introduces the following changes to the List: New events - WebAdding, WebProvisioning, ListAdding, ListAdded, ListDeleting, ListDeleted Site Collection events Synchronous "after" events to perform post-processing Custom error pages New property PSEventPropertiesBase to store the user name and token of the person who triggered the effective action New integrity constraints based on the lookup Projected Fields - fields from the parent which are referenced and displ...

Never use the IQueryable<T>.Where extension method when querying ListItem objects. The reason is that the client object model first evaluates the result of the CAML query, retrieves the results, and then filters the resulting collection using LINQ. If you filter a very large list using LINQ instead of CAML, the client object model attempts to retrieve all items in the list before filtering with LINQ and either issues queries that require too much system resources, or the query fails. T...

Using SharePoint 2007 on Windows Server 2008 might bring additional steps to configuration that didn't exist in Windows Server 2003. On of the most questioned area is "why I can't save Office Document to the SharePoint Library"? On Windows Server 2003 you can create new Office document via Document Library toolbar and save this document back to Library directly from the Office. However, in the SharePoint instance on Windows Server 2008 you will be asked to save the document to the hard drive. ...

 SharePoint Server 2010 adds a default OrderBy clause to SPQuery call that orders the result set by content type, which ensures that folders are returned before list items. For SharePoint Foundation 2010 you need to include of the three OrderBy clauses—ContentIterator.ItemEnumerationOrderByID, ContentIterator.ItemEnumerationOrderByPath, or ContentIterator.ItemEnumerationOrderByNVPField when using SPQuery Source: http://msdn.microsoft.com/en-us/library/ee558807(office.14).aspx

SPQuery object of SharePoint 2010 can fail or block results if we don't limit the result set. This object is used to query list and other collection objects, and it performs well when we set the number of returned values. Quering large lists without limit will block the results of SPQuery or it can perform very slow. Depending of the edition of SharePoint (Server or Foundation) limit the SPQuery using the following methods/parameters: RowLimit  ContentIterator.MaxItemsPerQuery (Serve...

Question: >> How can I convert List Template to a Feature Answer: The way to achieve this to use use Visual Studio Extentions for WSS to extract List Resources and then deploy them either via VSeWSS or via STSDEV Guideline http://dotnetdeveloper.co.uk/blogs/sharepoint/archive/2009/02/18/deploying-custom-lists-with-stsdev.aspx Tool http://www.microsoft.com/downloads/details.aspx?familyid=FB9D4B85-DA2A-432E-91FB-D505199C49F6&displaylang=en#filelist  

SharePoint 2010 Site Changes Role/Rule based Audience Targeting – added rules-based audiences, WSS groups and distribution list membership. Sites are collection of pages - SharePoint 2010 sites became more page-focused rather than a collection a lists. Sites still contain the same list and libraries as previous versions of SharePoint, but the site is now a collection of pages. Pages are optimized for Reading – all WCM pages are optimized for the reading, rather than for the writing, ...

To open a List in edit mode and add the new Web Parts you usually need a SharePoint Desinger. But there is a trick, how to open a List in Edit Mode and have the “Add Web parts” window is displayed. Everything you need to do is to add  "ToolPaneView=2" parameter to the List URL. For example, if you have the Forms list with the following URL http://t1:85/Pages/Forms/AllItems.aspx, applying the new parameter to the URL as http://t1:85/Pages/Forms/AllItems.aspx?ToolPaneView=2 you get the foll...

It is important to realize that SharePoint stores a complete binary copy of every version of your document in the SQL Server database. If the "Require Check Out" option is not enabled and a user forgets to check out the document first, a new version will be created every time a user saves the document to the server. This can lead to hundreds of versions of a document over time. But, if the document is checked out before it is edited, all changes will be saved to the same checked-out version ...

Question: >> I am trying to export a list to excel, but the "assigned to" column does not export. I suspect it is because there are multiple selections, but I don't know how to fix this Answer: This is a known issue for Excel 2003, because excel doesn't support importing columns with the multiple selection. Unfortunately, there is now fix as I know, and the only way to make such export is to use Excel 2007 and above.

SharePoint provides Auditing functionality to track what happening with sites, collections and farms via audit settings and policies . Unfortunately, there are no OOTB features, providing detailed item-level audit - how much times site items were viewed, copied, deleted and etc. The good side is that SharePoint object mode provides you API to implement custom audit for your site items. Everything you need is to obtain a reference to an SPSite object for the current site collection, and then s...

When a list or library has a large number of items, you must carefully plan its organization and how users need to access the data to help preventing adverse effects on performance. For best performance, do not exceed 2,000 items in a list level. For example, the root of the list or a single folder. In case if you must create and browse large lists, use the following best practices. 1) Create Indexed Column (An index on a column enables Microsoft Windows SharePoint Services 3.0 to quickly anal...

SharePoint provides you "Export to Spreadsheet" feature across almost all list, allowing you to export your list content to Excel. But not all lists have such functionality. For example, this option is not available for User list. It is either hidden from the toolbar menu in "People and Groups" http://[site]/_layouts/people.aspx (left picture), or User Info view has no toolbar http://[site]/_catalogs/users/simple.aspx (right picture) But there is a trick, how to export list of users t...

There are several standard columns, like "Title" and etc, which can't be delete from lists.  The workaround for this in creating the custom content type list and hiding the "title" column there. Step-by-Step instructions described there: http://www.bloggix.com/blogs/microsoft/archive/2008/07/06/how-to-create-a-custom-list-with-your-own-content-type-getting-rid-of-field-title.aspx