Thank you so much @Scott ! I’ve been testing though and at least in 2.38.4.3 there seem to be some limitations/issues to implement your recommendation:
-
On the first Predictor I had to slightly modify it for it to work, when using ==“yes” that was not working so I had to use ==1, which worked like a charm and then I had some meaningful values…
-
However, the second predictor is giving me 0 predictions when running. If I got it properly:
-
We must run the analytics between the 1st predictor execution and this one, I guess that because the second predictor will read from the analytics tables to aggregate 1st predictor output DE to quarterly level.
-
We configure it as quarterly and running as district level, saying that data source can come from OUs below the ones selected
-
In the formula for the generator we configure the average of the output DE for the predictor 1:
-
And then… that’s mostly it:
I don’t get any prediction for this second predictor… any thoughts on how that could be possible? Should I test in other newer versions of DHIS2?
Thank you so much for your help!