Moving standard changes from Test environment to PROD

[jean-pauldehaas]

Hi,

we have created some new standard changes in our TEST environment, and i would like to move them up to production but i dont know what is the best way to do this.

i feel like when i use an updateset it does not move everything.

any suggestions ?

thanks

[Community Alums]

Hi @jean-paul.dehaas ,

Use these procedures to create, test, and move customizations from a development system to a production system.

Three-step import process

A common process for developing customizations with update sets involves moving changes from development, to test, to production instances.

1. Create an update set on the development instance.
2. Make customizations and changes on the development instance.
3. Mark the update set as Complete.
4. Log in to the test instance and retrieve the completed update set from the development instance.
5. Commit the update set on the test instance, and test customizations thoroughly.
6. If the update set has problems in the test instance, repeat steps 1 - 5 to develop the fix on the development instance with another update set.
7. Log in to the production instance and retrieve the completed update set from the development instance. If the update set required a fix, retrieve both update sets.
8. Commit the update set on production. If the update set required a fix, commit both update sets in the order they were made.

Two-step import process

If your development environment consists of only two instances, you can combine your development and testing instances into a single staging instance.

1. Create an update set on the staging instance.
2. Make customizations and changes on the staging instance.
3. Mark the update set as Complete.
4. Test customizations thoroughly on the staging instance.
5. If the update set has problems, repeat steps 1 - 4 to develop the fix on the staging instance with another update set.
6. Log in to the production instance and retrieve the completed update set from the staging instance. If the update set required a fix, retrieve both update sets.
7. Commit the update set on production. If the update set required a fix, commit both update sets in the order they were made.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[jean-pauldehaas]

Hi sandeep ,

i know how to work with updatesets, i found some info that moving standard changes trough updatesets does not pick up all the info the standard changes need

[Community Alums]

Except data, scheduled jobs, groups the update set should capture most of the items. This is the best practice.

But if you are note sure then you can try moving the XMLs too.

Mark my answer correct & Helpful, if Applicable.

Thanks,
Sandeep

[Community Alums]

Hi @jean-paul.dehaas ,

Glad to see my answer helped you, Kindly mark the answer as Correct & Helpful both such that others can get help.

Thanks,
Sandeep