I have a 2007 SharePoint site called Beta. On Beta, I have a custom List called MapData. This is a custom list of data that a webpart reads from. Data has been typed into Beta to make sure the webpart works correctly.
In production, called Prod, I have that same List called MapData except it has old values. How can I copy the data from one site to another. Beta and Prod are on different servers. I would like to do this without writing C# or something. Is it possible use the command line to just backup that list and restore it on a different server or possibly use Sharepoint designer?
The following options are not without drawbacks, but they are codeless:
If the list is not too large, you can save it as a template, copy the .stp file from Beta to Prod, and create a new list based on the template.
STSADM has export/import
Gary LaPointe's custom STSADM command for this job: http://stsadm.blogspot.com/2007/11/import-export-copy-and-delete-lists.html
I'm actually looking to sync the two lists.
I need one to be the data that the public can see, while the other (parent list) has all of the public and private data.
Related
Why do we need a list definition to create custom list in visual studio?
I can create a custom list using the UI without the need for visual studio.
So what is the advantage of using a list definition to create a custom list in visual studio?
The UI can only create a list on a single server, in a single site. You can't copy this list to a different server, eg. to deploy it from your development machine to the production server.
It's also difficult to use the same list in different site collections or web applications. While you can save a list as a template, you can only use this template in the site collection it was created in.
The only way to define a list that you can easily deploy to multiple servers is by creating a list definition. Otherwise you'll have to backup and restore your entire site from one server to the other, or use third party tools that will do essentially the same thing.
Deploying using a list definition can take seconds. Deploying by backup/restore can actually take days, as SP will only warn you that something went wrong only AFTER the entire restore process has finished.
Furthermore, there are form customizations that can't be done without modifying the actual list definition, eg. hiding columns. If you create the list through the UI you'll have to use a third party tool to make the modifications.
Would also add, when doing development, you will need a procedure to migrate your code from DEV ennvironment to Your UAT environmet and then onto Production envirnment
If you do this manually it will take some time, also there is always a risk you have not created it the same way.
using list definations will make sure it is the same on each environment
Is it possible to move complete SharePoint site content to another SharePoint site? If Yes how it can be done?
There are a few methods that come to mind for moving data between sites
Using a third party solution which does all of the hard work for you, i.e. Axceler's ControlPoint
Save a list or library as a template, including its content, and then take the template over to the new site.
If you're looking to move an entire site or web, you can backup/restore or export/import via PowerShell
Write a custom solution that moves the data per list/item
HTH
i'm using Sharepoint 2010 and i want to create a List in a new Site, which contains Lists from the other sites.
Like a Global Overview.
Our problem is that we're using several sites with Ticketsystems. So i want to create a global list which contains all tickets from all other sites. (For sure just if they got rights to the Ticketsystem).
Is there a way to do this?
Regards
Alex
You can easily create a ticketingsystem in SP2010 with the following steps:
1. create a content type for the ticketsystem
2. add an itemreceiver to the content type
3. create a list for the ticket system
4. add contenttype binding to bind the content type to the list
5. deploy the list to the rootweb as well as all the subsites by adding the list through a webtemplate for instance
The itemreceiver you add should be an itemadding which would place a newly created ticket in the subsite also on the rootweb level. This would allow you to have all the tickets on the subsites and one allcontaining list on the rootsite level.
As far as I know there is no generic way of mixing references from another list in a new list.
You can either integrate and copy list items from your ticket systems into a "central ticket system" or create a custom control that reads from all ticket systems and displays them in the blend you like.
There is custom development in either way.
Begin by having a look at the Data View Web Part
http://office.microsoft.com/en-us/sharepoint-designer-help/display-data-from-multiple-sources-in-a-single-data-view-HA010099144.aspx
http://www.learningsharepoint.com/2010/10/16/create-dataview-webpart-in-sharepoint-2010-tutorial/
There is also the Content Query Web Part
http://msdn.microsoft.com/en-us/library/ff650512.aspx
The SPSiteDataQuery class lets you run a CAML query for all lists/libraries in a single site collection. It's pretty trivial to tie that to an SPGridView control to get a ListView-like user interface.
Internally this is what the Content Query Web Part users, so it has many of the same limitations.
Here's a reasonable example
I need to transfer a reusable Workflow from the stage env. to the prod.
The workflow is associate to a list, so the list id is stored in the workflow.
Is it possible to transfer the workflow and change the list id to the list name with Visual Studio? (We have no SharePoint Designer access to the prod. env.)
Short answer: No
I tried several hours to fix a reusable workflow, which same as yours was associated with a specific list - I switched systems and the GUID changed --> Workflow was broken.
You can give it a try and rename the MyWorkflow.wsp to MyWorkflow.cab and extract that somewhere. The workflow files are XML based hence you can edit the associated list GUID with your favorite editor. Now you need to package your edited file back into a cab file, rename it to wsp and you can give it a shot. I tried exactly that and resented to just "re-clicking" (as it's SPD) my workflow (two screens come in handy here).
That's what I call "reusable" workflow... Next time do not associate your reusable workflow with anything to keep it reusable.
I would recommend creating an Content Type in a Feature and then base your list and your Reusable Workflow association on that Content Type. We had a project in December where we successfully used this method. I saved a Reusable Workflow as a template. I then deployed the Content Type solution package and the Workflow solution package to another environment. Worked like a charm.
There are tow alternatives for deploying workflow regardless the assigned content types
It is very simple just do the following:
Alternative One
Save the workflow as template
Go to the following path in your site
http://your_server_Address/SiteAssets/Forms/AllItems.aspx
Download the file as WSP
Go to the following URL
http://your_Target_server_Address/_catalogs/solutions/Forms/AllItems.aspx
Upload the WSP, and activate the solution
Go to the site settings, then Site Actions, then Manage site features
Activate the feature that is related to the workflow
If you click workflows under site administration you would be able to see your custom reusable workflow
Alternative Two
Save the workflow as template
Go to the following path in your site
http://your_server_Address/SiteAssets/Forms/AllItems.aspx
Download the file as WSP
Open your visual studio
Click add new project
Under SharePoint choose 2010
Choose Import reusable work flow
Follow the wizard
Project will be created and can be deployed
Note : Make sure your workflow is reusable and that it has no errors
I am not server admin on one of our production systems, neither do I have SQL permissions because of this I need to ask someone to install a WSP package, its annoying.
Is there a way I can copy a list instance from one server to another by just using the SharePoint GUI, I am root admin on 1 machine (dev) and site admin on another (test/production)
I guess in the way that an information worker would do it, not a developer.
Thanks
On top of my head there 2 methods to move/copy a list
By using a list template -> Save the list as a list template and then create a copy of the list by using that template
Must have < 10 MB of list data
User must have Manage Lists Right site on both source and destination site
The source site and the destination site must be based on the same site template.
By exporting a list to a spreadsheet -> Export data to excel and the import to destination site.
Useful when list has > 10 MB of list data
Source and destination site can have different site templates
User must have Manage Lists Right site on the destination site
Works for moving a list between sites in the same site collection or in different site collections
All copied lists will be custom lists in the destination Web site
Microsoft office online has more details on how to copying or moving SharePoint lists
You can save list as a template (and choose to include data). See list settings - it does have an option. Template is saved in List Template Gallery, from which you can save it on desktop then import somwhere else and create new list based on this template.
You can also use some nice stsadm extensions to copy/move lists, webs, items, etc.
Yes, you can export your list and then import it back into the new server.
You do this by saving your list as a template (Go to Site Settings/Site libraries and lists/Customize list name you want to export)
When you get to this screen you can click on the "Save list as template". Fill out all the fields then make sure you click the 'Include Content' box and click 'OK'.
To import the list you go to your new server, and then go to Site Settings/List templates. You need to upload your saved template.
Go back to the Site Settings screen, and then go to your Site libraries and lists and then choose the 'Create new content' and choose the saved template. That should create a new list with all the content from the other server.
The only couple of caveats are these: You need to be the site admin to upload the template and create the list, and the list you are trying to create a template of must be under 10MB. There are ways to increase that size but I've never tried them.
Alternatively you can look at this blog posting for a pictorial view of how to do this:
http://grounding.co.za/blogs/neil/archive/2008/10/05/moving-a-list-with-content-between-sharepoint-servers.aspx
You can also use SharePoint Designer and Copy > Paste