I’m working on a decently large tracker program, and got some questions regarding ProgramIndicators:
It looks like ProgramIndicator can only refer to DataElements, not other ProgramIndicators (like “aggregate” Indicators can) - is there any specific reason for this? Will this constraint be left at some point in the future? Building indicators on top of other indicators is quite handy
Are the programIndicator results linked to running the analytics (when viewing them in the Event Manager app)? I tried to test that one, but was not totally sure of my results (as the pivot table & browser are doing a lot of caching too)
Thanks!
Martin
···
**Martin Van Aken - **Freelance Enthusiast Developer
I’m working on a decently large tracker program, and got some questions regarding ProgramIndicators:
It looks like ProgramIndicator can only refer to DataElements, not other ProgramIndicators (like “aggregate” Indicators can) - is there any specific reason for this? Will this constraint be left at some point in the future? Building indicators on top of other indicators is quite handy
Correct, program indicators cannot refer to other program indicators. We do consider supporting this in the future.
Aggregate indicators can refer to program indicators though.
Are the programIndicator results linked to running the analytics (when viewing them in the Event Manager app)? I tried to test that one, but was not totally sure of my results (as the pivot table & browser are doing a lot of caching too)
Yes it is.
regards,
Lars
Thanks!
–
**Martin Van Aken - **Freelance Enthusiast Developer
Ok so: programIndicators have a more powerful evaluation engine (with the d2:condition for example), but indicators can use other indicators.
What I’m not 100% is the consequence of using a (aggregate) indicator to compose program indicators - is it still possible in this case to compute values “per event” or will it only work for aggregated values per org unit per period?
Martin
···
On Wed, Feb 21, 2018 at 11:56 AM, Markus Bekken markus@dhis2.org wrote:
Hey Martin!
You can make composite indicators that consists of other program indicators, but program indicators can not be nested within each other directly.
Yes- program indicator values are always based on the data in the analytics_* tables.
I’m working on a decently large tracker program, and got some questions regarding ProgramIndicators:
It looks like ProgramIndicator can only refer to DataElements, not other ProgramIndicators (like “aggregate” Indicators can) - is there any specific reason for this? Will this constraint be left at some point in the future? Building indicators on top of other indicators is quite handy
Are the programIndicator results linked to running the analytics (when viewing them in the Event Manager app)? I tried to test that one, but was not totally sure of my results (as the pivot table & browser are doing a lot of caching too)
Thanks!
Martin
–
**Martin Van Aken - **Freelance Enthusiast Developer
Ok so: programIndicators have a more powerful evaluation engine (with the
d2:condition for example), but indicators can use other indicators.
What I'm not 100% is the consequence of using a (aggregate) indicator to
compose program indicators - is it still possible in this case to compute
values "per event" or will it only work for aggregated values per org unit
per period?
No unfortunately not per event.
···
On 21 February 2018 at 12:12, Martin Van Aken <martin@joyouscoding.com> wrote:
Martin
On Wed, Feb 21, 2018 at 11:56 AM, Markus Bekken <markus@dhis2.org> wrote:
Hey Martin!
- You can make composite indicators that consists of other program
indicators, but program indicators can not be nested within each other
directly.
- Yes- program indicator values are always based on the data in the
analytics_* tables.
Markus
21. feb. 2018 kl. 11:03 skrev Martin Van Aken <martin@joyouscoding.com>:
Hi DHIS2 dev team!
I'm working on a decently large tracker program, and got some questions
regarding ProgramIndicators:
- It looks like ProgramIndicator can only refer to DataElements, not
other ProgramIndicators (like "aggregate" Indicators can) - is there any
specific reason for this? Will this constraint be left at some point in the
future? Building indicators on top of other indicators is quite handy
- Are the programIndicator results linked to running the analytics (when
viewing them in the Event Manager app)? I tried to test that one, but was
not totally sure of my results (as the pivot table & browser are doing a
lot of caching too)
Thanks!
Martin
--
*Martin Van Aken - **Freelance Enthusiast Developer*
Ok so: programIndicators have a more powerful evaluation engine (with the d2:condition for example), but indicators can use other indicators.
What I’m not 100% is the consequence of using a (aggregate) indicator to compose program indicators - is it still possible in this case to compute values “per event” or will it only work for aggregated values per org unit per period?
I’m working on a decently large tracker program, and got some questions regarding ProgramIndicators:
It looks like ProgramIndicator can only refer to DataElements, not other ProgramIndicators (like “aggregate” Indicators can) - is there any specific reason for this? Will this constraint be left at some point in the future? Building indicators on top of other indicators is quite handy
Are the programIndicator results linked to running the analytics (when viewing them in the Event Manager app)? I tried to test that one, but was not totally sure of my results (as the pivot table & browser are doing a lot of caching too)
Thanks!
Martin
–
**Martin Van Aken - **Freelance Enthusiast Developer