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

Uploaded Date data in other formats
I am trying upload data from a CSV with date. For size reasons, I don't want to dimension the module by date but bring it in as a line item formatted as date. The problem is that person that will be doing the upload is in Italy, and their date format is different. When she does the upload, the date gets messed up…
Anaplan Level 3 Assign accounts to territory
Hi, when I am assigning the account to the territory I am always facing error as below and account never get assigned to the territory , what could be the reason ? When I use same method for unassign it works .
An Update on Anaplan Audit Log Reporting: A No-Code Approach
A while back, I shared a pattern for extracting and reporting on Anaplan audit data using a Python project hosted on GitHub. I wrote that during my time on the Operational Excellence Group (OEG) at Anaplan. The Python solution still works, and plenty of teams are running it today. The problem it solves hasn't changed:…