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.
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: I was trying to identify which models consume our Data Hub as a source in a model-to-model setup. Anaplan supports using one model asβ¦
1. Idea description Enable Excel-like filtering for Date fields in Anaplan.Currently, Date filters only support conditions (e.g. equal, between), requiring manual input.It would be helpful to have a value-based filter where users can select specific dates from a list using checkboxes. 2οΌExample of enhancement In Excel,β¦
It would be very useful to have an option to change the model at the App level. Currently, we need to switch models individually for each page, even when they all belong to the same model. Instead, there should be a way to change the model once, and have that update applied across all applicable pages within the App
