Transfer update sets

[Koji Yanase]

We have now about 160 local update sets and 3800 update records. Each update set is based on each story. And for example, the same flow X or the same form layout Y are modified in different update sets.

We need to now transfer all updates from the development to the production instance. Is there any good method?

Merging all update sets is fine?

[James Chun]

Hi @Koji Yanase,

Merging them in a single Update Set should be fine unless you have used multiple application scopes.

Do you have another sub-production instance, such as a Test instance?

If so, I highly recommend you to test it before deploying it to Prod.

Cheers

[Koji Yanase]

Hi, James,

Thank you for your reply. I heard the number of update records in the update set shoud be less than 2000. Would it be still a problem?

[James Chun]

Hi @Koji Yanase,

Do you mind sharing the link where it states the above?

Also, if you are worried about it being too big, maybe you can group them in multiple batches (e.g. batch per sprint).

Cheers

[Tai Vu]

Hi @Koji Yanase 

Update Set Batching be yer key!

Batch update sets enable you to group update sets together so you can preview and commit them in bulk.

Dealing with multiple update sets can lead to problems, including committing update sets in the wrong order or inadvertently leaving out one or more sets. You can avoid these problems by grouping completed update sets into a batch.

Ref: Update set batching

Cheers,

Tai Vu