Catalog Builder update sets - Do I need them all?

[spike]

In Tokyo, Catalog Builder now creates a self contained update set with your changes when you create or update a Service Request.

If create a new SR I get update_1 (example name - bears no relation to actual name!).

If I then update that SR I get update_2.

Assuming I've not promoted anything to the next environment, does anyone know if I need to apply both updates sets or whether I can just go with update_2?

Thanks!

[Chris Cardenas]

We are experiencing the same issue and have the same question. Our Catalog builder created multiple update sets with each following update set containing more total customer updates than the previous all showing as 'Complete'

Would we have to apply all created update sets or just the last one from Catalog Builder?

[spike · Accepted solution]

I've now managed to do a test on this with our Admins.

We had four update sets for a single SR in Dev. It had been published to dev and edited three times afterwards, hence the four update sets.

We took the last update set that was created and promoted that to our UAT system. It seems to have deployed everything we wanted.

Therefore I conclude if you have multiple update sets created by the catalog builder for a single SR, then you only need to promote the last one to get the SR into another environment.

[CecileC]

What is the best thing to do if you need to make some change in that same catalog later ? 1 or maybe more update sets will be created... Even though you push only the last update set created, is there a risk for all the variables to be doubled?

[spike]

I think you need to be a little careful if you're deleting something, say a task or permission.

I'm sure I had a problem where I did one change (deleted a group that the SR was available for) and then made a second change in a second update set. We put the second one through and the deletion didn't make it into prod. I think. I didn't really record exactly what happened at the time.