Issues around Catalog Builder update sets

[Russell Abbott]

I ran in to an issue when using Catalog Builder in Tokyo, freshly upgraded. I had created an update set, lets call it 'my_update_set', set it as current. Created a new Catalog Item. Made some changes to it after initial creation.

I noticed the creation of the Catalog Item was captured under 'my_update_set', then some updates were also captured under a system created update set called 'CB_xxxxx', where xxxxx is a date/timestamp.

When I came to move this to TEST, it had duplicated some items, other items were not what I was expecting.

My question I guess is, was there a need for me to create 'my_update_set'? Or should I just have created the Catalog Item, set the 'CB_xxxxx' update set as current, then proceed to make my updates to that one?

I'd be interested in how you guys have worked with this, it looks like it's a new feature under Tokyo.

Thanks!

[surajmesinane]

Facing Similar Issue would like to know why the system update set got created and what is the work around to move update set.

[Russell Abbott]

The system update set is created as a new feature from what I gather. The workaround, if I want to continue to make changes using the Catalog Builder, then I have to continue to use the CB update sets that get generated each time I make a change in the Catalog Builder application.

If i prefer not to use the Catalog Builder, you can ignore that update set and use your own update set.