Sounds useful. Please create a jira issue.
Knut
On Jun 7, 2017 4:11 PM, "Petar Jovanovic" wrote:
> Hello everybody,
>
> We have in our DHIS2 instance data elements belonging to different
> programs/data sets, but also to different domains (packages) or diseases we
> are dealing with. Also, some
Using groups is a good idea, but still we cannot use it for searching
and accessing data elements in the maintenance app.
Petar
On 07-Jun-17 4:38 PM, Jason Pickering wrote:
Seems like a good feature and I think it's planned. Maybe you can use
data element groups to accomplish the same purpos
Seems like a good feature and I think it's planned. Maybe you can use data
element groups to accomplish the same purpose?
On June 7, 2017 4:11:13 PM GMT+02:00, Petar Jovanovic
wrote:
>Hello everybody,
>
>We have in our DHIS2 instance data elements belonging to different
>programs/data sets, b
Hello everybody,
We have in our DHIS2 instance data elements belonging to different
programs/data sets, but also to different domains (packages) or diseases
we are dealing with. Also, some of them are common across different
diseases and domains.
So far, in order to easy the search for speci
Hi Johannes
Please direct any questions about DHIS2 to the dhis2-users list which is
copied in this mail.
The default credentials for DHIS2 instances is
Username: admin
Password: district
If you start a new DHIS2 instance up that is the default credentials or if
you access the demo site
Hey Stanley,
currently thats not possible to do exactly as defined below. When using the
enrollment analytics type, the repeated events is "flattened", so you can only
query the newest data value for each data element within each program stage.
You would have to model your data for the purpose i
6 matches
Mail list logo