Is it possible to do Switch over on a daily basis versus a monthly basis?
@neg177
Two approaches, both use DISCO, neither use switchover:
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.
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!
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?
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?
I'm going to give option 1 a try.
Thank you
Good choice! Good luck and let us know how it turns out. Anxious to hear.
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?
Yes, that looks correct. Let me know if you need an example.
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
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…