We are having some issues using aggregated indicators in 2.25.
‘VN SAN - 3.3 % latrines meeting quality standards’ is an indicator containing ‘VN SAN - # latrines meeting quality standard’ as numerator and ‘VN SAN - 3.1 # latrines installed confirmed field visit’ as denominator.
I can have a look but need some more info. Could you please provide privately:
a dhis login to the server.
a link to the indicator in the maintenance app or API.
a link to a pivot table which illustrates the problem (0 output value).
best regards,
Lars
···
On Thu, Nov 3, 2016 at 5:20 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:
Dear all,
We are having some issues using aggregated indicators in 2.25.
‘VN SAN - 3.3 % latrines meeting quality standards’ is an indicator containing ‘VN SAN - # latrines meeting quality standard’ as numerator and ‘VN SAN - 3.1 # latrines installed confirmed field visit’ as denominator.
For the record, the problem here turned out to be use of the default option combo explicitly in the indicator numerator, while the data being collected for non-default option combos.
In indicators, if you want the total value for a data element, one should use this syntax:
#{deuid}
and not
#{deuid.cocuid}.
Lars
···
On Fri, Nov 4, 2016 at 11:00 AM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Jose,
I can have a look but need some more info. Could you please provide privately:
a dhis login to the server.
a link to the indicator in the maintenance app or API.
a link to a pivot table which illustrates the problem (0 output value).
best regards,
Lars
–
On Thu, Nov 3, 2016 at 5:20 AM, Jose Garcia Muñoz josemp10@gmail.com wrote:
Dear all,
We are having some issues using aggregated indicators in 2.25.
‘VN SAN - 3.3 % latrines meeting quality standards’ is an indicator containing ‘VN SAN - # latrines meeting quality standard’ as numerator and ‘VN SAN - 3.1 # latrines installed confirmed field visit’ as denominator.