@Shaik22 Here are the answers to your questions.
1. Limitations of update sets: The biggest limitation is that an update set cannot capture updates across the different application scopes. In order to capture updates across different application scopes, you need to create multiple update sets catering to each application scope.
2. Update set best practices:
- Always create an update set first before start working on any customisation. Never make changes in the default update set.
- Try to create a batch update set if you are working in multiple application scopes
- Merge multiple update set and create single update set if they are created in a single scope.
- After previewing an update set on the target instance, make sure to address all the errors/conflicts(if any) on the target instance.
3. Ways to move update sets from one instance to another: Following are two ways by which you can move update sets from one instance to another.
(i) Export as XML:- After setting the state of an update set to complete, you see an option to Export the XML of the update set.
In order to import the update set, you need to visit Retrieved Update set module on the instance where you would like to deploy this update set and use import update set link to import the update set.
Once loaded, you can preview and commit the update set on the target instance.
2. Import the update set via update source module.
You can use the Update Sources module to import the completed update sets on the target instance.
Which one to follow? The best way is to configure the update source, as once configured you will not have to import the update sets manually.
Hope this helps.
