What does this feature do? Unlink revisions created after this restore point. Go to Model History > Choose a restore point > it pops up.
Hey @DaanishSoomar
It's a new feature recently released by Anaplan. If you use Application Lifecycle Management (ALM), and you restore a model to another point in its history, you are now able to unlink any revision tags between the two model IDs. It means that workspace administrators can restore compatibility between dev and prod models when previous changes to production have made them incompatible.
If after doing a sync, a change via revision has introduced a bug in the prod model. You can now restore and unlink to before the sync and then fix it in the dev and then reintroduce a fresh change.
Cheers!!
Hi @chp127
@david.savarin is right.
This is what you need to follow, after rev 2 is pushed to prod and you want to undo it:
This feature can also be used to clean up your rev tag history from the dev by removing the unnecessary pile up of revision tags which are not synced but also no longer needed
Hi @Himanshu1998 ,
Could you please elaborate how it works in prod? can you provide any real scenario.
Lets take below scenario:
1st Scenario :
2nd Scenario :
For your first scenario, i think you need to restore the prod model to the previous revision tag
This is necessary to keep compatibility between the 2 models :
βThe latest revision in target model must exist in the source model.β
Thank you for explanation, but its same scenario 2 and what about data lose in prod ?
Hi All
Hopefully by now you've had chance to test out this quite helpful functionality. But if you're still wondering it basically allows you to restore your deployed model to before the most recent sync point (just remember to tick the box), do the fix in the DEV model plus revision tag and then sync the new revision tag through to deployed model.
If you forget to tick the box then the sync breaks.
@Himanshu1998 I personally wouldn't undeploy a deployed model - you should just be able to roll-back the DEV model, do a new revision and sync that to PROD.
@chp127 yes you would lose production data because you're restoring the model to a point in time as all the calculations have been changed
Hi all,
Great topic. What if I want to go back in history of my prod model before a revision tag just to review some data and then revert it? Can I use this new feature, not breaking the connection, and then return all production and structural data back?
@andrewtye @Himanshu1998 Finally got into an issue and had to search for this topic. A couple of questions:
@ankit_cheeni
Yes, if you have to revert your production model to a history id then this will lead to production data loss as all the calculations would have been changed
I used this future mistakenly, not the DEV is no longer compatible with the production. Not sure how to deal with it.
I am trying to create a Net Debt / EBITDA formula at the bottom of one of our P&L income statements where, i have tried the MOVINGSUM function. However this does not work for summary line items which EBITDA is. What i would like is to be able to sum the previous 12 months EBITDA (Including the current period) numbers in aβ¦
I have this template to import back to my module By right it should match the module because the time format is the same as the module the only difference is that in the excel file there is a seperator. M-Y. Thus logically to me it should be But when i run the action using M-Y and match names both result in an import errorβ¦
Hi everyone, I was trying to Retrieve a Line Item (Boolean) using TIMESUM as formula to another module by using ANY. This Boolean LI has A,B,C as dimensions. My target module has only A as dimension. In order to use a reference module for mapping, does this reference module had to have A,B and C as dimension or just Aβ¦
