Lars, is there an intention to fix this bug in 2.15 ? I understand that the Web
API is being rewritten but this is a major bug. Or is 2.15 not to be regarded
as a stable release, with the userbase being encouraged to move directly to
2.16?
- Edward -
On Sunday, July 6, 2014 7:17 PM, Lars
Hello Lars,
As you know, we are still investigating the DHIS system to see if we can use it
in our organization.
Actually, we started implementing a small pilot project in one country area and
we are trying to collect the data and move it into DHIS and then analyze it and
create some reports.
One possible solution is to simply transform your data directly to a form
which can be imported directly into the database itself. If you are doing
a one off or supervised data import, it should be relatively simple to
transform the data to import to SQL and inject it directly, while this
feature
Hi Robin,
its a good question and actually something that has been discussed before.
You highlight some of the pros and cons in your email.
The reason why we haven't done it so far is simply that we want to avoid
the complexity that comes with validity dates instead of routine time
periods and
Hi Edward,
I'm sorry but we don't plan to fix this. If you let us know your use-case
we are happy to suggest a work-around.
regards,
Lars
On Tue, Jul 22, 2014 at 9:32 AM, Edward Ari Bichetero ebich...@yahoo.com
wrote:
Lars, is there an intention to fix this bug in 2.15 ? I understand that
Hi Maheed,
I agree with you. I have implemented it now in trunk for XML and CSV. Will
be part of 2.16. You can try it from the CI server in 40 min:
https://apps.dhis2.org/ci/job/dhis-trunk/
regards,
Lars
On Tue, Jul 22, 2014 at 10:42 AM, Maheed Ramadan maheed.rama...@nrc.no
wrote:
Hello
Hi Channara,
There are four kinds of datediff formulas supported :
*1.* Incident date diff : Get the number of days between a data element and
incident-date of tracked entity instance ( TEI ). Below is an example for
this case :
* DATEDIFF([DE:1.2.3] , dateOfIncident) 1*
*2.* Enrollment date
Hi all developers,
MY SUGGESTION:
In “section grey field management” of combo category options. Has only “Disable
field” for disable entry value. But I think it is important, we should have
“Hide field” to hide some combo category. Because it effect on showing in Data
Entry, if we has many
Related to this, we have a big form where most sections are very simple
and broken down only by gender, but one is also broken down by A LOT of age
groupings, so the auto-generated form becomes extremely wide and the users
have to scroll a lot horizontally. This also means it is very easy for them
No, the DATE attributes haven't supported in aggregate builder. I sent
email to Oslo to discuss about supporting it for version 2.17.
Best regards,
Châu Thu Trân
HISP Viet Nam
Email: tran.hispviet...@gmail.com
On Wed, Jul 23, 2014 at 11:05 AM,
YES knut, custom forms is good for user can do any things to design and assign
any DE to show. but the main problem of custom forms is when I go to report →
dataset report. I can’t export in excel or pdf. It work only printing function…
From: Knut Staring
Sent: Wednesday, July 23,
Hi Robin,
in the 'DHIS world' we distinguish between
- data elements, ('data variable', 'count'), which is may be regarded as an
atomic unit / raw piece of data, such as in your case cases of patient
encounters by diagnosed disease and by gender (gender / age group will
typically be defined as
Hi,
I faced a similar issue when I was customizing DHIS2 tracked instance to
collect patient-based data for the cancer screening clinic in Sri Lanka.
(DHIS2.15)
In our case, client details are collected for registration and then for the
visit clinical history, examination, investigations and
13 matches
Mail list logo
