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; } } }

Can Switchover be used on a Daily basis?

neg177

Is it possible to do Switch over on a daily basis versus a monthly basis?

Accepted answers

JaredDolich

@neg177

Two approaches, both use DISCO, neither use switchover:

Use the native versions in one module (Module A). One for Actuals, one for Forecast. Add another module (Module that contains the current date. In Module A you'll add a line item that has this format: IF PERIOD(START()) >= Module B.Current Date THEN Sales[SELECT: versions.forecast] ELSE Sales[SELECT: version.actual]
Same as 1, except you'll denormalize the forecasts and actuals and create a separate line item for each instead of using the native versions. Your formula will look something like this: IF PERIOD(START()) >= Module B.Current Date THEN Sales Forecast ELSE Sales Actual

One nice thing about option 1 is that you can make the actuals read only and forecast editable using the feature to apply formula to a version.

All comments

JaredDolich

@neg177

Switchover will follow your model calendar. Lowest a model calendar can go is weeks.

To get switchover to daily, you'll most likely need to create a module to hold the current date. That can be automated, by the way using Anaplan Connect. Once you have the current date you can use formulas to determine the switchover. To be honest, this is the method I use because I don't want to have a casual Anaplan user have to become a workspace adminsitrator to change the switchover. Hope that helps!

neg177

Ok, What are other routes I can go with Forecasting? Can I have my Module with just Actuals and then a Module with just Forecast? Or would the Switchover be a better bet?

neg177

I guess the real question I'm trying to ask is what is the best technique to approach when Forecasting a Daily Model in Anaplan?

JaredDolich

@neg177

Two approaches, both use DISCO, neither use switchover:

Use the native versions in one module (Module A). One for Actuals, one for Forecast. Add another module (Module that contains the current date. In Module A you'll add a line item that has this format: IF PERIOD(START()) >= Module B.Current Date THEN Sales[SELECT: versions.forecast] ELSE Sales[SELECT: version.actual]
Same as 1, except you'll denormalize the forecasts and actuals and create a separate line item for each instead of using the native versions. Your formula will look something like this: IF PERIOD(START()) >= Module B.Current Date THEN Sales Forecast ELSE Sales Actual

One nice thing about option 1 is that you can make the actuals read only and forecast editable using the feature to apply formula to a version.

neg177

I'm going to give option 1 a try.

Thank you

JaredDolich

@neg177

Good choice! Good luck and let us know how it turns out. Anxious to hear.

neg177

In the formula IF PERIOD(START()) >= Module B.Current Date THEN Sales[SELECT: versions.forecast] ELSE Sales[SELECT: version.actual] , sales is referring to the line item I want to forecast?

JaredDolich

@neg177

Yes, that looks correct. Let me know if you need an example.

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…