Hello Elmarie,Forgive me, but I am not sure where to set the aggregation start
level.
For the reports, what we have started to do is to select org units at levels
(Comprehensive, Satellite, and Outreach) when we noted this issue. I do not
know if this is a wrong method.
But this is a big concern
Hi Jan,
I am checking with the team that owns this instance for permission to share
the database with you and will get back to you.
Thanks,
Lorill
On Tue, Aug 16, 2016 at 12:45 AM, Jan Henrik Øverland wrote:
> Hi Lorill,
>
> We are looking into ways to speed up the loading of option sets. Any
Hi Ifeanyi,
You should not set an aggregation start level then analytics will aggregate
from the lowest level up. Only if you have set a start level to e.g. OU4 then
it will only use values captured from OU4 and above to higher levels so that
now does not seem like your problem.
I am so
Hello Elmarie,The thing is, I'm not sure exactly where that setting is made for the analytics. If you could provide a clue, I can go and check to see if we have the wrong setting. You have been quite helpful.
Hi,
We are working on DHIS 2.24 branch (revision - 23565). We have created a
chart on one DHIS instance and imported it into another DHIS instance. All
the other metadata entities sync well, except for charts. The same happens
with Pivot Tables, Event reports and Event Charts and maps as well. The
Hi,
We are working on DHIS version 2.24 (revision - 23565). We are testing the
behaviour of restricting data Sets through User Roles. We have created a
user role with all the authorities, except 'ALL' authority. And did not
assign any data Sets to this user role. Then we assigned the role to a
use
6 matches
Mail list logo
