Move documents along with versioning

Keep in mind that below approach works only within the site collection level.  I mean to say here is it is not possible to move the documents between libraries across site collection levels.

The best approach to move the documents between the libraries along with versioning is using “site content structure” option. 

Note: But one thing we should keep in mind that versioning shoould be enabled in both the source and destination document libraries.

Steps to move the documents between document libraries:

Step1: Go to Site Actions -> Site Settings.  Under “Site Administration” click “Content and structure”

Step2: Find the source library and select the all or any specific documents you want to move and then click “Actions”à Move.

That’s it. Now, go and visit the destination document library. You will get the moved documents along with its versioning’s.

One thing I observed here is, along with the documents versioning, metadata also would came.

I have a created a source document library and created 3 custom columns with different types. Uploaded the new document along with the metadata and then moved this document to destination library.

In addition to the versioning in destination library  what ever the columns available in source got created the same in destination( means 3 custom columns which are all created by me on source library are also available in destination library).

Source library:

Destination library:

Happy Sharepoint.

Please take a momenet and do comments if this post really helps

SharePoint list view web address is not displaying the absolute URL

Issue: SharePoint list web address is not displaying the absolute URL:

Description: Recently, we migrated SharePoint 2010 applications to 2013. While doing content validation in SP2013 to check whether all the metadata is migrated properly, we found an issue that most of the list web address is not showing the complete view URL. It is just showing web application URL.

Solution: You will face such type of issues if no view set as by default to the list. Check the list views and set any of the view by default and check, it will show the complete view URL.

Regards,
Sasi Kumar Reddy

sharepointquicksolutions.blogspot.in

Sharepoint interview questions with answers: lists and library

I had faced below listed issues while doing migration from SharePoint 2007/2010 to 2013:

Quick Edit view issue:

http://www.sharepointdiary.com/2014/12/fix-quick-edit-disabled-in-sharepoint-2013-issue.html

Quick Edit view: Result: Get "Assertion Failed: Break into debugger?"

http://www.brandmysharepoint.de/quickedit-in-listen-wirft-javascript-meldung/

We applied the JavaScript at master page level, issue solved.

“Files” and “library” option are not available by default in ribbon for document library:

Issue is it will be disabled if you add any web part to the OOB pages (like CEWP)

By default, SharePoint limitation for Size of URL is 260 characters.

You might get the below exception if exceed the limit:

Exception: The specified file or folder name is too long. The URL path for all files and folders must be 260 characters or less (and no more than 128 characters for any single file or folder name in the URL). Please type a shorter file or folder name.

Note: Microsoft recommended size limit for single file name is 128 characters and URL limit is 260 characters.

I have uploaded one document to the document library and when I open it through browser the size of the URL is 258 characters(max limit 260) and later on I have changed the web application “http://India.com” to http://allindia.test.IND.com and now my the document size of the URL is 263 characters(means exceeded the limit). My Question how the SharePoint handles these types of scenarios?

As per my analysis: you can’t edit/download the document but we can view the document through browser.

View the large number of records in SharePoint list/library:

We can view the large number of records (around 1lac) by removing the filters, group by/sort by and select the “Show items without folders” option.

Export to excel the list item with attachments:

We can achieve it by using the "Open with access" option. From there if wants we can directly download from the access.

Export to excel the list item with attachments URLs:

We can achieve it by using web service concept in Nintex

Export to Excel”. Keep in mind that you can’t export a list that has more than 52,000 items;            

http://lyndzhang.wordpress.com/2012/09/27/working-with-large-lists-in-sharepoint/

Copy/Move items from one list to another list in sharepoint

Scenario:

List AA fields: Name, Title, User Name, Religion, Qualification.

List BB fields: Name, Title, User Name, Qualification, Designation, Salary and Description

Common field names: Name, Title, user name, Qualification

Now, I want to copy the common field values from List AA to List BB.

Approach:

//Read the list item values by ID and add the common field values as new item into the another list

SPListItem spLstItemsAA = listNameAA.GetItemById(ItemID); //ItemID of List AA

SPListItem spLstItemBB = list.Items.Add();

foreach (SPListItem spLstItemAA in spLstItemsAA.ListItems)

{

       for (int i = 0; i < spLstItemAA.Fields.Count; i++)

       {

          if ((!spLstItemBB.Fields[i].Hidden) && (!spLstItemBB.Fields[i].ReadOnlyField) &&    

                                  !(customfields.Contains(item.Fields[i].Title)))

           {

               spLstItemBB [item.Fields[i].Title] = spLstItemAA [item.Fields[i].Title];

             }

        }

 }
 spLstItemBB ["Salary"] = "50k";
spLstItemBB ["Description"] = "sharepointquicksolutions.blogspot.in ";
spLstItemBB.Update();

Condition#1: !spLstItemBB.Fields[i].ReadOnlyField

Condition#2: !spLstItemBB.Fields[i].Hidden

The above 2 conditions are used for to skip the read only and hidden fields.

Note: By default, every sharepoint list and library will have the below fields.

List doesn’t exist. The page you selected contains a list that doesn’t exist. It may have been deleted by another user

Recently I encountered the below issue while trying to recreate the same document library from the template.
“List doesn't exist. The page you selected contains a list that doesn’t exist. It may have been deleted by another user.”

Scenario: I got a requirement like recreate the same document library which is already present.
Approach: Save that document library as template and recreate wherever/how times you want. I did the same thing. But I got the above exception when I tried to recreate the same document library by referring the template.

Solution: Check the enterprise keyword column is used in the document library. Delete it and recreate it again.

I did the same thing and it’s works fine.

-Thanks,
sasi Kumar Reddy

How To: Create nth level of Folders in SharePoint document library programmatically c#

Create nth level of folders creation in SharePoint document library:  

Requirement:  Recently I have got one requirements i.e. create 2 levels of folder creation in the SharePoint document library means create a root folder and sub folder inside it.

Solution: I started development to support 2 levels of folder creation but I thought later on what to do if users may come back with 3 levels of folder creation. For that reason I have developed to support up to nth level folder creation.

e.g.: Folder creation levels

Level 1: /Document library/ Folder/

Level2:  /Document library/ Folder/Sub Folder/

Level3:  /Document library/ Folder/Sub Folder/Sub Folder/

Nth level:  /Document library/ Folder/Sub Folder/Sub Folder/..................../ nth sub folder