Answered by:
Setting up a test environment for a list

Question
-
I'm a SPF admin. who's learning as I go. I came into SPF after our admin. left suddenly and I got the job with no knowledge of SPF, although I'm learning pretty quickly.
We've got a corp. site with a Project Request list we're getting to roll out and my boss asked me about a dev./test/QA environment for future changes. So, this is a request for a "SharePoint For Dummies" level procedure for setting up a test environment for this list and any future lists.
We've got a test site and I'd like to able migrate between it and our production site. So what I'm looking for is the process by which I could have a Project Request list on our test site that I could be working on (modifying workflows, InfoPath forms, adding/removing fields from the list, etc.) and be able to roll out changes to the production Project Request list without effecting the data in the production Project Request list?
Friday, February 7, 2014 12:03 AM
Answers
-
Though moving stuff from dev to prodution is very tricky when there are data in the production and I use multiple approaches based on the changes -
1. For the workflow, you can configure xoml files to move to production or try to use reusable workflow when it is possible. Reusable workflows can be easily deployed to different servers, and one catch is the name of the solution , which you can import to visual studio or open the files name the solution accordingly.
2. Moving lists and libraries, I use WSPs and Powershell
3. for InfoPath, you can simply publish the form to the production server, that would update the content types and column changes if any without affecting the data
you can also refer to this forum thread to http://social.technet.microsoft.com/Forums/sharepoint/en-US/1d7a69cc-2a22-4bd7-b63e-3944847f075d/move-the-whole-sharepoint-from-test-to-deployment
http://social.technet.microsoft.com/Forums/sharepoint/en-US/1272c877-6b16-4a3d-a531-a037cadea748/deploy-sharepoint-team-site-to-production
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if the reply helps you
- Edited by Ramakrishnaraja Friday, February 7, 2014 7:37 PM
- Proposed as answer by Hemendra Agrawal Tuesday, February 11, 2014 5:40 AM
- Marked as answer by Hemendra Agrawal Friday, February 14, 2014 6:33 AM
Friday, February 7, 2014 7:34 PM
All replies
-
Hi Frank,
I would suggest you setup an VM (Single server farm - http://www.microsoft.com/en-us/download/details.aspx?id=29073). You could also take the backup from the production site and restore it to your VM.
How Do I: Backup and Restore a SharePoint 2010 Site Collection? (video) http://technet.microsoft.com/en-us/video/backup-and-restore-a-sharepoint-2010-site-collection.aspx
This would enable to test your Proof of concept.
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if the reply helps you
Friday, February 7, 2014 2:08 AM -
Well that gets me a dev. environment, but how do I go about rolling out changes to production without overwriting the data in the production list??
How does SPF handle the addition/deletion of fields when you roll out a change??
Does the restore include workflows (a lot of what I've seen online indicates that it doesn't) and customized InfoPath forms?
Does the restore include any custom solutions I've built?
Friday, February 7, 2014 4:47 PM -
Though moving stuff from dev to prodution is very tricky when there are data in the production and I use multiple approaches based on the changes -
1. For the workflow, you can configure xoml files to move to production or try to use reusable workflow when it is possible. Reusable workflows can be easily deployed to different servers, and one catch is the name of the solution , which you can import to visual studio or open the files name the solution accordingly.
2. Moving lists and libraries, I use WSPs and Powershell
3. for InfoPath, you can simply publish the form to the production server, that would update the content types and column changes if any without affecting the data
you can also refer to this forum thread to http://social.technet.microsoft.com/Forums/sharepoint/en-US/1d7a69cc-2a22-4bd7-b63e-3944847f075d/move-the-whole-sharepoint-from-test-to-deployment
http://social.technet.microsoft.com/Forums/sharepoint/en-US/1272c877-6b16-4a3d-a531-a037cadea748/deploy-sharepoint-team-site-to-production
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if the reply helps you
- Edited by Ramakrishnaraja Friday, February 7, 2014 7:37 PM
- Proposed as answer by Hemendra Agrawal Tuesday, February 11, 2014 5:40 AM
- Marked as answer by Hemendra Agrawal Friday, February 14, 2014 6:33 AM
Friday, February 7, 2014 7:34 PM