Snapshot

BlueSky-Wind chaser

Hi,

 

I have a scenario where I have to take a snapshot every week(forecast periods) -max 6 weeks forecast period.

 

 

Source Module -Standard Time Scale, Article List, LineItem(which I want to take a snapshot) 

Target Module- Standard Time Scale, Weekly snapshot LIST(Contains list member of Lag 1, Lag 2, Lag3..6), Article List, LineItem(Where the snaps will be stored)

 

Every week when I run the Action to capture the current week data it has to be in lag 1 always. Lag 1 data should be moving. 

 

Instance, this week when I'm running the action to copy the data to fixed list member of lag 1. I want the previous week data to be moved to other lags. 

 

Current Week - Lag 0 (Fixed)

Previous Week- Lag1

A week before Data-Lag2 

 

I want help on how to move the data from one lag to other lag (Lag is a list member).

jasonblinn

@aishabhy05 

I would try at all costs to not have to move the data, but instead, just have dynamic references. This way you run the snapshot process one time and it should be much lighter on performance than forcing all of the data to move and cause Anaplan to have to re-calculate everything. 

 

Here is an idea. I obviously don't have all of the details so hopefully, this will spark your imagination a little!

 

Instead of having my Snapshot list of Lag 1, Lag 2... etc. I am making my snapshot list be related to the current week of the model. In this case, I am using the current date to calculate the current week. Let us assume that the snapshot gets ran every Friday in this example.

Name of the list items are the Date (Fridays). The week number becomes the code.

 

From there, I have a module where I am able to snapshot my data into: (In this example my data is identical from each snapshot version)

 

Now I need to be able to reference these snapshots to bring into my final formulas, so I need to be able to calculate what week should be Lag 1, Lag 2, etc. 

As you can see I am driving these snapshot items formulaically since I can calculate them based on the current week, thus, Each week I get a new snapshot and my Current week updates, so there is no additional maintenance to worry about. 

 

Finally, in the final reference module You just have a line for each Lag, and Lookup the reference module we just covered.

 

I hope this gives you some ideas! Let me know if you have additional questions, or if this does not meet your needs.

 

Jason

 

 

BlueSky-Wind chaser

Thanks @jasonblinn  . Gave me a good insight into the thought process (about performance) and will try to figure out the solution with the inputs shared. 

johnsondavid

To move from one delay to another, you need to review your documentation to see if it is suitable for what you need, like me playing Geometry Dash Scratch must see if it is suitable for me before playing, not just like it, because doing so often causes unexpected errors, I wish you soon find the answer for yourself

BlueSky-Wind chaser

@johnsondavid I guess I have mentioned on my comments to Jason that it gave me good insights on the solution shared by him. OfCourse, based on the requirement I have applied the suitable solution along with the thought process shared by Jason.