Hi!
Can the model history be restored after executing a delete using selection action deleting a bunch of items (around 50 million items) from a particular list?
The model is in the standard offline mode.
Thanks,Somain
Hi Somain,
Although this number is huge, I don't see a reason why this shouldn't work. I've tried it before with a smaller number of deleted items and it worked fine. Try to find a point in history before the action was performed and restore the model.
Cheers,
Dmitry
@somain.gupta you can easily restore your module back to the way it was but there are some caveats.
1. Any changes you made after you ran the delete action will also be lost because you are restoring the model back to the state it was in before you deleted the items.
2. offline/online doesn't matter. Offline only prevents other admins from editing your model. It does not save any memory in your workspace.
3. Because your list is rather large it may take Anaplan a little while to restore the model.
Here's how you can do it:
First, I built 500 list items and added my sales to a few of them.
I took my model offline.
I deleted the list with 500 members
Go into history and select the transaction just before the delete action and restore the model.
You will be take out of the model. Upon opening again, you will see the data has been restored.
I wanted to check if others are facing this specification difference between Grid Card in Additional Insight. When created using a Saved View, the Quick Sum bar feature does not work, but when created using the module directly, the Quick Sum bar works.
Does anyone have any documentation on the trade-offs of having 1 model for all components of planning (service revenue, product revenue, labour planning), vs multiple models 1 for each and a consolidation model to tie it all together?
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…