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.
Idea Description As a model builder, I want dependent dropdown rules to be enforced consistently across all data-entry methods, so that users cannot enter values that would otherwise be unavailable through the configured dropdown selections. Example of Enhancement I'll know this is successful when values that do not meetβ¦
Problem In Management Reporting, the number of columns in a Table card is fixed when the card is created. When a dynamic filter returns a different number of items (e.g. fiscal years depending on the selected Version), the card does not adapt: If the card was created with few columns, additional items (e.g. FY29) neverβ¦
Allow end users to apply multiple sort levels on a single grid in UX pages, so they can organize data across several dimensions without workarounds. Thank you,
