Skip to main content

Migrating Lists - Using list templates SharePoint 2013

Recently I came across a strange & unusual behaviour in SharePoint 2013. I was moving stuff from the dev environment to production. One of the most basic task is to move lists. So the usual process of taking a list template from dev to production and creating a list out of the list template.

But, Microsoft decided that we will not allow this from SharePoint 2013. Let developers learn some (unnecessary) new stuff. So, the above mentioned basic concept of moving a list will not work in SP 2013. I have absolutely no clue as to why.

So the new approach is to use powershell script to create list from the templates. Its a HACK I know, but MS still allows us to do it.

First you have to save the list as template and then upload that to production list template gallery.
Then change some values below and run it in PowerShell. Thats it, you list will be created.

# Get the SiteURL
$site = get-spsite("http://YourSite/")
  
# Get the Articles web
$web = Get-SPWeb -Identity "http://YourSite/SubSite/"

# Get the custom list templates
$CustomlistTemplates = $site.GetCustomListTemplates($web)
  
  
#Create the custom list using template
$web.Lists.Add("YourList", "YourList", $CustomlistTemplates["Your_List_Template"])
  
Write-Host "Based on the template YourList Created"

$site.Dispose()
$web.Dispose()


Thanks to Santosh Babu for the detailed writeup.


Happy Learning
Vighnesh.





Comments

Anonymous said…
Hello Vighnesh,

Please REMOVE the Background ..Content is NOT visible at all..

Thanks.
Johnson

Popular posts from this blog

Error while activating feature - SharePoint 2010

Hi all, While I was working on SharePoint 2010 recently I came across some issues. I am putting them across so that anyone facing the same issue may find solution easily. Error: Error occurred in deployment step 'Activate Features': Feature with Id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' is not installed in this farm, and cannot be added to this scope. Solutions: I was getting this error while ‘deploy’ing a feature from Visual Studio 2010. I searched the entire project for this GUID which is mentioned in the error. I did not find it anywhere. While troubleshooting, I opened the physical folder and opened ‘Feature1.feature’ file in notepad. This xml file was using the before mentioned GUID. I was not able to find it in VS 2010 :( I copied the GUID mentioned in the ‘Feature1.feature’ file and pasted it in the Feature ID section in ‘Feature1.Template.xml’ file. This solved the problem. Why I thought to mention it is because the exception thrown is confusing. It does not tell you...

Working with large xml files in c# .net

Working with large (huge) xml files is always a pain in the … The reason? These files can’t be loaded in to memory. On my desktop, where I have 2 gigs memory, I can’t open the file in even notepad. I was presented with a challenge recently to manipulate one such large xml file. The xml file was of 550+ MB. I know many would say I have seen bigger xml files than this. But the heart of the matter is if I can’t open 550+ MB file in notepad or in xmldocument in c#, then I can’t open any file bigger than this. And hence the logic to play with these files would remain same. The scenario: We have an xml file from which we want to remove a single node without removing its children. In the below sample xml fragment, the node has to be removed. The children nodes, must then be attached to ( node’s parent) node. One Two 100.22 GoodDay 3 4 Five 200.09 Cra...

Custom People Picker (Editor) in SharePoint 2010

[Modified:11 Oct 2010] Now you can find the source code for this example in CodePlex The out-of-the-box SharePoint people picker allows users to select users, SharePoint groups, Distribution Lists & Security groups . Users may accidentally add large AD groups to SharePoint groups and send notifications to hundreds of people. The administrator may want more control over the security of the people picker control. In some scenario the administrator may want to restrict the user to only select ‘users’ or ‘SharePoint Groups’. This can be achieved by creating a custom people picker control which inherits from SharePoint people editor. In below example, we are going to explore creation of custom people picker control, replace the OOTB people editor control, provide a people picker settings page in central administration and create menu to access the settings page in Central Administration. 1. Create custom people picker For creating a custom control (which inherits from SharePoint PeopleE...