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 have a Price module where customers are ranked based on their unit prices. I also have a Comparison module, where I want to display the names and unit prices of top-ranked customers for comparison. The model includes a Customers list. In the Comparison module, I want to write formulas to bring in the customer names and…
Can there be a duplication in Process ID's
Client has spoke models built in Classic and now considering building Data Hub in Polaris in order to deal with sparsity. On the surface this seem possible but likely a bad idea. Has anyone done anything similar to this? Specifically, what did you have to do to ensure that data was compatible? Any thoughts or suggestions…