Update Set

[Rooma1]

Hi All,

I have been asked in an interview that if there are 100 of records in an update set, how can we move 50 today and 50 next week?

Thanks,

Rooma

[SanjivMeher]

I dont know if we can do that and I dont think we should do that. If it has to be separate, 2 separate update sets should be created and then imported in batches. Imagine, you have 100 records in an update set, how would you choose what to import and what not to. So i guess the answer is best practice would be to create two separate update sets and capture the changes separately, so that the changes are migrated to other instances smoothly.

[Mark Roethof]

Hi there,

So what was the question you asked back on that 😅 I mean who would ask something like that, really weird question.

[Sumanth16]

Hi Rooma, 

It is not possible to do that. Create two separate update sets and move 50 customer updates which need to move next week.

Please appreciate the efforts of community contributors by marking appropriate response as correct answer and helpful, this may help other community users to follow correct solution in future.

Thanks & Regards,
Sumanth Meda

[Tony Chatfield1]

Hi, the simple answer is that you cannot part deploy the content of an update-set.
But you can move selected updates to another update-set, meaning that you can create a second\independent update-set -as long as the updates left in the first set are not dependent on them.

First create a new update-set in the same scope as the update-set that you are working with.
Then open the original update-set
Open the 'Customer Updates tab in a new window

Add the 'Update set' field to your list view (if not visible)

From the list you can now select\change the update-set that the update belongs too, so you can move the 50 updates you want to hold back into your new update-set.
Once finished complete and deploy both update-sets as normal.