how to move records from default update set to a different update set?

raking08 · ‎07-30-2015

Of course doing one at a time is easy.. but I need to move about 300 updates currently in default along with many updates from other projects. I need to move my dev to test on a different schedule so I need to move these records for customer updates to a new update set and was hoping there might be a way to do this in a mass update. The usual table editors (i.e. change selected records) are not available.

Does anyone have a simple idea short of changing one at a time?

Many thanks

Tanaji Patil · ‎08-07-2015

FYI...

Yes you can move the updates in bulk.

1> Open your update set

2> Go to Customer Updates related list

3> Right click on the filter i.e. Update set = Default and open it in a new window

4> Now check if you can see 'Update set' column there. If not then personalize and add it.

5> Use filters to just have the records need to moved.

6> Using 'shift+down arrow' you can select all the records and change the value of the update set to target update set.

This will move all your selected updates records from the current to target update set.

Hope this is what you need.

Thanks,

Tanaji

View solution in original post

bernyalvarado · ‎07-30-2015

Hi, some thoughts:

a) I would not recommend trying to modify the update set field of the update. This could give you big problems, specially with workflows

b) One idea would be to merge the 300 updates into a new update set. Would that work for you? I have never tried to merge updates from default before, but I believe that will be a good alternative for you.

Thanks,

Berny

raking08 · ‎07-30-2015

option (a) seems to be OK with forms.. just horribly slow.

Option (b) sounded great, but I cannot see how to merge a subset of records from one update set (Default) into another smaller update set. If you filter and select, merging to another set is not an option for selected records that I can find. Am I missing something? (probably)

bernyalvarado · ‎07-30-2015

Hi,

Point a) actually it was more of a warning. . I had situations on the past where moving the updates from one update set to another by manually modifying the update set field actually caused issues in the version that ended up been deployed to the following environment. I faced this situation primarily with workflow related changes

As for point b), you're totally right. This requires further digging to find out if there's a way to pick a subset of the changes as eligible for a merge. That will definitely be a nice feature

If you're manually going through each record, I consider that perhaps the best approach to move a change to a different update set could be by navigating to each "related record" and doing/undoing a change just to save the record within the desired update set. I earlier was going to suggest that this could be done through script but it might turn out to be a complex task with a considerable risk involved.

I hope this is helpful!

Thanks,

Berny

bernyalvarado · ‎08-07-2015

Hi raking08, would mind closing this thread by marking the responses as helpful/correct?

Thanks,

Berny