Moving customizations to another environment

(0) Share

Report

Posted on by bbbking

375

I have a development environment where I have multiple people making screen changes, building workflows, etc and would like an easy way to identify what those changes are and be able to copy or migrate those changes to our staging server...and eventually to the live server. Are there any recommendations on the best way to do this or tools that might assist with this process

*This post is locked for comments

All responses (3)

Answers (0)

Suggested answer

Hosk on at

Like (0)

Report

RE: Moving customizations to another environment

If you have a lot of development going on then it's a good idea to split the functionality into either logical solutions or sprints.

This will also have the advantage of being able to deploy the different solutions separately and be able to monitor what changes went into what solution and when it was deployed.

Also if you have one big solution it's very hard to know what changed and when and will take longer and longer to deploy.
RuneDaub 3,795 on at

Like (0)

Report

RE: Moving customizations to another environment

as MVP write, the best way is to tell your customizer to work with solutions.

In sprint (SCRUM based projects), I normally create a solution for each sprint, that can be released...
MVP 10 on at

Like (0)

Report

RE: Moving customizations to another environment

You should create a new solution and add your existing customizations and dependent objects to it. Then export your solution as either managed or unmanaged, I usually do one of each, and import the managed version into your staging and live servers.