How to Migrate a SharePoint List While Preserving its Metadata Properties like Modified date and modified time

Problem

Generally you open a document library in Windows Explorer view to move items/ documents in bulk to other document libraries. This approach doesn’t maintain the current item/document’s metadata properties like “Modified” (DateTime) & “Modified by”. The list items will get the current Date Time as “Modified” (DateTime) and the user who does the migration as the Modified By.

Solution

You would think of using Datasheet view to move list items but that doesn’t preserve item Metadata Properties.

You may even think of saving the list as template with content included and create your new list at the desired location out of this list template. But this doesn’t preserve the metadata properties either. The list items will take the current time in the "Modified" (DateTime) field and "Created by" as the user who created the new list.

The simplest solution is to use "Site Content and Structure" to migrate Lists!

Follow the steps to move your SharePoint List along with its Metadata properties:

1. Create the document library or your custom list at the destination. You don’t have to worry about the custom fields and list structure. The move process will take care of it.

2. Lets create a source custom list with a custom field "Comments" as shown below:




3. Create some dummy data. Note the Modified date and time field values (Metadata properties)




4. Go to Site Actions → Site Settings → "Content and Structure" under site administration as shown below:




Or for a publishing site, you can go to Site Actions → "Manage Content and Structure" as shown below:




5. Open your source custom list and select all items to be moved, as shown below:




6. This opens up the Move dialog box. Select the Destination Custom list in which you want to move your list items
Note: "Destination_CustomList" list doesn’t have custom field "Comments"









7. Go to the destination list → you will see that all content has been moved and custom fields have been created. Add the custom field "Comments" in your view.
Below is the "Destination_CustomList" snapshot:




As shown in the above figure, you can see that this process preserved Metadata properties of listitems and also created the new custom fields.

Provide anonymous access to sharepoint lists on Office 365 (Sharepoint online)

Problem:
Due to version upgrade in cloud office 365- Sharepoint Online from 2010 to 2013 anonymous access option is not showing and also setting up contributor rights not working.

Solution:

Steps to configure a sharepoint list on my public facing sharepoint site that is accessible for anonymous users:

1. Download the anonymous365 sharepoint solution from http://anonymous365.codeplex.com
2. Go to the “Site Settings” of your public facing site using by example :
   http://sample/_layouts/settings.aspx
3. Go to the “Galleries” section and go to “Solutions“.
4. Click under the “Name” colume and in the ribbon interface under the “Solutions” tab choose “Upload Solution“.
5. Browse to the previously downloaded anonymous365 sharepoint solution : “Wsp365.Anonymous.wsp” and press “OK“.
6. Check the checkbox of the uploaded “Wsp365.Anonymous.wsp” and in the ribbon interface under the “Solutions” tab choose “Activate“.
7. The go to the “All Site Content” of your public facing site using by example:
   http://sample/_layouts/viewlsts.aspx
8. Press “Create“
9. Choose the list type you want, enter a name and press “Create“.
10. Then in the ribbon interface under “List Tools” and “List” press the button “Anonymous Access“
11. Choose what access you want to give anonymous users for this specific list and press “OK”.

Client Object Model Solution Issue due to framework 4.5 version: The type or namespace name 'SharePoint' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?

Solution:

Whenever we create a new project(console,wpf..etc) in Visual Studio 2010,It is targeted to use .net framework 4.0 and SharePoint 2010 need .net framework 3.5 as Target framework.
So solution is simple just go to the properties of your project and change Target framework to .NET Framework 3.5 and you good to go.

Features and their GUID’s in SP2010

Gotten tired of finding the ID of a feature? 

Please visit given below site: 

http://blogs.msdn.com/b/mcsnoiwb/archive/2010/01/07/features-and-their-guid-s-in-sp2010.aspx

A great deal of time and effort!