Is it possible to have period start/end selectors to pick the run rate period instead of a moving average? Each time we add actuals it changes all the forecasts making previous adjustments and overrides obsolete requiring re-work.
Hopefully this answers your question... you can have a look-up module (the start/end line items and would put these separately) which you can reference against as per the images. Means that if you want to have Jan-Mar as your movingaverage you can and it not be impacted by actualisation. You've got to be dynamically creating the offsets dependent on the time period you're in - this will also work for weeks too just need to change the formatting.
Hi @therealwarsi
Can you please explain the problem statement a bit better? Some of us may not be aware of the problem statement.
I would like users to select which month or months they want the run rate to include in the average from prior months for forecast. Therefore unless this is changed by the user it would remain static even if we add actuals for a month.
For example:
- We are forecasting 8+4 for a GL account and users picked months 6,7,8 as their run rate using Booleen checkboxes for months 9-12. If I add September actuals and change the switch over date, I don't want Anaplan to automatically change the run rate to be 7,8,9 using a moving average. Hope this makes more sense.
Glad I could help!
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…
