PlanIQ Backtest data automation and Backtest data should come for all Actual periods as we import data let's suppose of 60 months for forecasting of 3 months then Backtest result come out for only past 3 months not for 60 months
We cannot produce backtest for all the history because it works differently.
Let's assume we have 24 months of historical data and we want to forecast 6 months ahead.
When algorithms are training, PlanIQ will take the 24 months of history and split it into two parts. First 18 months are being used for training. The latter 6 months are being withheld from training process and during the model creation, PlanIQ is actually "forecasting" this period. The "forecast" produced is then compared to 6 months of actuals that were kept on the side. This is how quality metrics are generated.
As a result, we cannot provide backtest information for the entire history.
However, if you write backtest results into the same module where you will be writing your forecasted values, you will be able to continuously track performance of PlanIQ forecast compared to your actuals - as you are adding more actuals and generating more forecasts.
Hope this helps.
Current Challenge In Anaplan XL, the Allow Writeback option is currently configured at the workbook level and must be enabled separately for each new workbook or grid. For teams that frequently use writeback functionality, this creates repetitive setup work and increases the risk of users forgetting to enable the setting…
Financial planning models are constantly evolving throughout Forecast and Budget cycles. New requirements, model enhancements and business changes are essential to support better decision making. However, these ongoing developments can create a challenge when approved numbers used for management reporting remain directly…
Problem Statement Currently, Export Actions and Saved Views are not dynamically synchronized after an Export Action is created. This limitation creates additional maintenance effort for model builders and increases the risk of inconsistencies between export configurations and reporting requirements. Key Challenges 1. Saved…