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?

[Koji Yanase]

Hi, Timi,

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?

[Amarjeet Pal]

Hello @Koji Yanase ,

Hope you find this helpful. 

A large number of updates in a single set might slow down the commit process and make it harder to identify issues if something goes wrong.

The figure of 2000 you mentioned is often suggested as a guideline rather than a hard limit

Keep the Number of Updates per Update Set Small

Leading off of the previous section, I don’t like update sets containing a large number of customer updates for a couple reasons:

Update sets become convoluted
If you are trying to remove unnecessary updates from an update set, it is much easier to identify these updates when there are only a few entries to go through.​

Troubleshooting update set conflicts becomes much more difficult
With large update sets, it becomes an inevitability that conflicts will arise. Especially when you have multiple developers on your team all making changes to the same instance. Of course there are exceptions to this, such as when developers are working in different application scopes or are using team development. If this bullet point doesn’t apply to your team you should disregard this point.​

I don’t have a hard rule of thumb for the maximum number of updates an update set should contain, but things seem to get more difficult when the update count passes 100, and especially difficult when it passes 1,000. If you follow the “one update set per user story” guideline, you should rarely, if ever, have more than 1,000 updates in an update set. If you find your update sets having more than 1,000 updates on a consistent basis, you probably should go back and rework your stories so they are more granular. If this isn’t an option, you might consider splitting large update sets into smaller parts.

Thanks

Amarjeet Pal