ALMing multiple revision tags into Production environment

priyamshah

Hi,

I have a scenario wherein I have multiple revision tags ALMed from Dev environment to the UAT environment. They have been synced in the correct order.

I now need to sync to Production with UAT environment. I understand that revision tags are cumulative in nature but wanted to understand any possible implications of syncing the latest revision tag in UAT into the Production environment. and not sending every tag from UAT to the Production in the same order.

jasonblinn

Hi @priyamshah -

Your understanding is correct, syncing the latest revision tag will take all of the cumulative changes from the previous sync and make them. In General, that is probably the outcome you are looking for.

The only scenario I can think of where you might want to run multiple back to back is the event when you need to Change an Input, or retain entered information. In this case, the Order of operations does matter in regards to the outcome. Example below.

Let say that I have a requirement to change my Input value to be at the lower level.

Here it is at the Parent Level:

Option 1: All changes in one Sync

Change 1: Update Formula to not look at Parent

Change 2: Update Input Value Line item dimension to match the rest of my data:

You can see here, the numbers all changed in the input which gives me different costs, which i dont want. This might then require an import or user intervention to correct data…

Option 2: Use a multi part Sync

I can Use ALM to my advantage here by doing a multiple part sync to retain the data.

Here i started with the first screenshot. I would simply create a new line here to take the data down a level. Since i havent changed anything else, I could sync this with no adverse effect.

Now I can re-write the formula for Cost to look at my new line item, and remove the formula from the new line.

I have successfully transformed the input without losing data or having to run import actions. There was also NO Downtime, or time when the data was incorrect.

As you can imagine in a small example like this, it might be silly to do this, but if you have thousands or millions of cells it can be a nice way to handle situations like this.

Hope this helps!