SharePoint Migration: Migrating a page having DataViewWebPart from SharePoint 2007 to SharePoint 2010

Migrating a page having Data View Web Part from one server to a different server


I got this issue while moving the lists with MetaLogix Migration Manager. It’s a very common issue I have seen people struggling with. Time to fix these issues increases if count of DVWP increases.

By default, SharePointDesigner binds the control to the list instance using the list instance GUID. To resolve this we need to replace the GUIDs by the list name.

The steps to do this are:

1) On the attributes of the DataFormWebPart element replace the attribute ListName="{GUID}" by ListName="LIST_NAME" where LIST_NAME is the name of the list that you are binding to.

2) Go through all of the DataFormParameter elements and replace: WebPartPages:DataFormParameter Name="ListID" ParameterKey="ListID" PropertyName="ParameterValues" DefaultValue="{GUID}"

With:

WebPartPages:DataFormParameter Name="ListName" ParameterKey="ListName" PropertyName="ParameterValues" DefaultValue="LIST_NAME"


3) Go to the ParameterBindings element and replace

ParameterBinding Name="ListID" Location="None" DefaultValue="{GUID}"


With:

ParameterBinding Name="ListName" Location="None" DefaultValue="LIST_NAME"


This should give you a GUID free DVWP that can be placed on a page layout used by multiple sites on your site collection (as long as the name of the list is the same on all sites).

Cheers!!!

The possible ways: File Share Migration in SharePoint 2010

The possible ways: Migrate file shares to SharePoint 2010

Now your client wants you to suggest something for the 50 GB contents which is lying on the file system. Users are fine with that and they don’t want SharePoint or your client will be more then happy to see these 50 GB contents in SharePoint and enforce users to follow WCM standards by leveraging SharePoint.

Option 1:  You can simply set up SharePoint and let users slowly migrate to it while supporting file shares at the same time. 

Option 2: By creating sites and using the Page Viewer Web Part, the team members can both access the SharePoint site for collaboration and access the read-only file shares. The good thing about this approach is, it feels like you are in SharePoint and using it’s security model. Though it’s correct and another good thing is, if you have imposed any security on your file system contents, it will follow that. J

Option3: Get a third-party tool like Quest Software's File Migrator for SharePoint, AvePoint's DocAve File System Migrator for SharePoint, and Metalogix's FileShare Migration Manager for SharePoint.

You can then decide how you want to proceed.  If your client is good to spend few thousand dollars buy a tool and do it or force users to adopt new platform or let them be there on file system and feel them like they are in SharePoint.

Cheers!!!

Suneet