I am aware that the Catalog Builder allows Catalog items to be saved in their own update sets. However, I have noticed several issues and would like some feedback.
1) Although it is quite useful for the catalog item to be saved in its own update set, we are noticing that not all information related to the catalog item is properly stored in the update set. Chief among them is any catalog client scripts that are involved in the Catalog Items. They are NOT stored in the update set that is automatically generated in the Catalog Builder.
2) We are also dealing with over 100 catalog items built via the Catalog Builder and having to deal with missing elements is becoming a pain in the rear.
We currently have a need to migrate these catalog items including some supporting code into our production system but we are unaware on how best to proceed on this. Migrating 100 individual update sets doesn't seem to be a good idea and merging them into one appears to result in a lot of errors that we are not able to deal with. It was suggested that creating an update set and forcing these Catalog Items into this update set may be a better course of action, however I am unsure as to how this might be accomplished.
Any ideas?
