Skip to main content

We have multiple clients using our software, and some of them may have a different version in production than other. In some cases, there is the need for data conversion because of new functionalities or restrictions. We encounter some risks when upgrading from different versions i.e. we have one client that is currently on version 6.300 and one on a slightly higher version 6.301.

We developer our conversion script for version 6.400, and place it in a certain folder. However, this come with some risks and we would like to manage our conversion scripts in the SF.

We already use the UPGRADE code group for scripts that have to be executed every upgrade, but in this case we need a script that will be executed in every upgrade that encapsulates version 6.400.

So in our examples, an upgrade from version 6.300 to 6.400 should have the script, but also from 6.301, or even if we skip version 6.400 and go straight to a 6.401.

The UPGRADE code group can be used to manage data conversion scripts for specific versions, but I am looking for a more wider range of version. 

How do other companies handle this problem, or is it already possible to manage in the SF?

The best way to do this is too handle all updates as a cumulative update. For example 6.300 → 6.301 → 6.400 → 6.401, and not skip versions like 6.300 → 6.400. You can reduce the overhead of having to perform multiple upgrades using the Deployer. The manifest allows you to have the Deployer automatically perform the necessary upgrades.

Terms & ConditionsCookie settings