Statistics
The Highest Post







Statistics
Count 94
Avg 21.00
Min 21
Max 21
Angualr Top questions

Details



Peter Agyekum Some common Pitfalls Of Update set? In addition to planning the process, make sure to avoid common pitfalls: <br> 1) Do not delete the Update set. If an Update set is deleted, any updated records may be overwritten in the next update.<br> 2) Do not back out the Default update set. This action causes damage to the system.<br> 3) Do not mark an update set as Complete until it is ready to migrate. Once an Update set is complete, do not change it back to In progress. Instead, create another Update set for the rest of the changes, and make sure to commit them together in the order that they were created. Naming conventions may help in this case (for example, Performance Enhancements and Performance Enhancements 2).<br> 4) Do not manually merge updates into an Update set. Always use the Merge Update Sets module. This tool compares duplicate files between update sets and selects the newest version.<br> 5) If a committed update set has a problem in the test instance, build the fix in another update set in the development instance. Commit this set to the test instance, and then make sure both sets are migrated to the production instance and committed in the order they were made.<br> 6) Always preview an Update set before committing it.<br> 7) Set completed update sets on the production instance to ignore. This state ensures the update set is not reapplied when cloning the instance.<br> 8) Keep a to-do list of manual changes and data loads that need to be completed after an Update set is applied.<br> 9) Do not make too many changes at one time. Verify that the correct changes have been made incrementally.
Related Topics