nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to keep current time scale data intact while moving to next Current period

sharmagh

Hi,

Just for my understanding, What I need to do in Anaplan so that when I change my current period (Q1) to next quarter (timescale Q2), my current quarter (Q1) data didn't not get delete and automatically covert to hard coded figures.

Thank you!

Accepted answers

Akhtar.shahbaz

Hi @sharmagh

I agree with @mikejorg , you can control from Version Edit to & Edit From, Another approach to control is through DCA.

If you have ALM, then I think DCA would be better and faster, you don't have to sync every time.

1. Create one system control module by quarter and one line item

2. Create another Module for DCA

3 Apply DCA in your input module:

Hope this helps!

Thanks

Akhtar

All comments

mikejorg

Hi @sharmagh ,

As long as you aren't looking to change the model calendar, you should be able to adjust the 'Edit From' and 'Edit To' fields in the versions part of model settings.

It doesn't exactly hard code the periods outside of these fields, but it does prevent them from being edited.

Akhtar.shahbaz

Hi @sharmagh

I agree with @mikejorg , you can control from Version Edit to & Edit From, Another approach to control is through DCA.

If you have ALM, then I think DCA would be better and faster, you don't have to sync every time.

1. Create one system control module by quarter and one line item

2. Create another Module for DCA

3 Apply DCA in your input module:

Hope this helps!

Thanks

Akhtar

alexpavel

@sharmagh Are you referring to the mechanism when you use on a version "Forecast the "switchover" flag?

I this case for "actual periods" the data are physically copied from "Actual" version on "Forecast" version and the previous "Forecast" values are lost. This mechanism cannot be changed.

What you can do is to create workarounds to preserve data of the "Forecast" version.

- copy data into another line-item that does not use "Use switchover" flag in modules before changing the current period

- create a custom mechanism to manage the "actual" and "forecast" months which does not use the "switchover"

etc...

Quick Links

Can you help?

Unanswered questions

How Can I Recreate Anaplan’s “Reporting Tips & Tricks” Showcase Model for Learning Purposes?
Anaplan Modelers: Has Anyone Recreated a Showcase Model for Learning Purposes? One of the most valuable learning resources I've come across is Anaplan's Modeling Showcase. It features sophisticated, real-world model examples that offer an incredible opportunity to learn how experienced model builders structure their…
Introducing Anaplan Toolkit: side panel for model details, exports and model lock tracking
Hi everyone 👋 If you build or maintain Anaplan models, you've probably hit the same walls I kept hitting. Some basic questions about a model's structure have no single screen to answer them. You end up clicking through modules and pages one by one, or writing API scripts just to get a list. These were the gaps that…
How to handle an Entity Structure change effective from January 2026 in Anaplan Consolidation & Repo
Hi Everyone, We have a requirement in Anaplan Consolidation & Reporting (Fluence) where the Entity Structure needs to change effective January 2026. The key requirement is that the existing entity structure should continue to be applicable for all reporting and consolidation periods through December 2025, while the new…