Thank you Lars,
Viet Nguyen, welcome to the very large DHIS2's family
Pepe Ken Mvulu
2016-02-06 3:18 GMT+01:00 Lars Helge Øverland :
> Hi all,
>
> Viet Nguyen has joined our team as software developer.
>
> Viet has 8 years of experience in Java software development in different
>
revno: 21893
committer: Zubair Asghar
branch nick: dhis2
timestamp: Fri 2016-02-05 17:28:34 +0100
message:
ProgramStage Completion BUG
modified:
revno: 21890
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Fri 2016-02-05 15:11:14 +0700
message:
minor fix to importer, make sure that non collection refs are propertly
updated
modified:
Please try again with latest 2.21 or newer, should be OK now.
--
Morten
On Fri, Feb 5, 2016 at 2:11 PM, archana
wrote:
> Thanks, Morten.
>
> Archana Chillala
> Application Developer
> Email archa...@thoughtworks.com
> Telephone +91 9100960533 <+91+9100960533>
>
Hi all
As the DHIS 2 for iNGOs Symposium 2016 is approaching, over 15 keynote
presenters, PSI, IPPF, Jhpiego, Akros to name a few, have confirmed their
participation. Check out the biographies:
https://www.dhis2.org/symposium2016-presenters.
You haven't yet registered? We still have a
You have to allow it I think
On Feb 5, 2016 9:32 PM, "Craig Hollingsworth"
wrote:
> Hi,
>
>
>
> Hope all are well and ready for the weekend!
>
>
>
> I’ve created an attribute of type date for use in tracker (v2.22). This
> appears to be unable to accept future dates.
Hi,
Think I might have found a bug in v2.22 Event Reports. Replicates on the play
AWS demo (snapshot).
Child Programme, Birth
If I run a report with data elements then works fine. If I include an
attribute then get no data back (I'm using gender).
No errors sent to console.
Cheers
Craig
Hi Devs,
I hope that someone will be able to assist with an issues around tracker.
We want to limit users on the dates for which they can capture tracker/event
data both on the program event/incident date.
DHIS 2 allows a setting to allow future dates but no limit on limiting past
dates.
Hi Devs
Our analytics process is failing with the following error:
[image: Inline image 1]
Any suggestions? This is a production DHIS2 instance which hasn't refreshed
analytics for 4 days. Please help...
Kind Regards,
Greg
--
*Health Information Systems Program - South Africa*
*- - - - - - -
revno: 21892
committer: Lars Helge Overland
branch nick: dhis2
timestamp: Fri 2016-02-05 13:17:21 +0100
message:
Data synch, code structure improvement
modified:
ps. 9295515 was the periodid (record) we deleted. The other duplicate
periodid was 9295516...
On Fri, Feb 5, 2016 at 2:19 PM, Greg Rowles wrote:
> We're running 2.19 but i found the duplicate. We had 2 period rows with
> the exact same values. I deleted the entry with no
OK, cache clearing worked, analytics now running ... thank you team!
On Fri, Feb 5, 2016 at 2:25 PM, Knut Staring wrote:
> In your datavalue table you will have references to the one you deleted.
> Update those to point to the remaining one
> On Feb 5, 2016 1:21 PM, "Greg
Great.
Always clear..
On Feb 5, 2016 1:27 PM, "Greg Rowles" wrote:
> OK, cache clearing worked, analytics now running ... thank you team!
>
> On Fri, Feb 5, 2016 at 2:25 PM, Knut Staring wrote:
>
>> In your datavalue table you will have references to
April 9 exists twice, it seems. Which version?
On Fri, Feb 5, 2016 at 1:03 PM, Greg Rowles wrote:
> Hi Devs
>
> Our analytics process is failing with the following error:
>
> [image: Inline image 1]
>
> Any suggestions? This is a production DHIS2 instance which hasn't
>
Dear Greg,
The issue is a result of the same date range (startdate - enddate) but
different periodTypes. Look for that.
Alex
On Fri, Feb 5, 2016 at 3:05 PM, Knut Staring wrote:
> April 9 exists twice, it seems. Which version?
>
> On Fri, Feb 5, 2016 at 1:03 PM, Greg Rowles
revno: 21891
committer: Lars Helge Overland
branch nick: dhis2
timestamp: Fri 2016-02-05 13:16:44 +0100
message:
Data export/sync, fixed regression bug with SQL / id schemes
modified:
We're running 2.19 but i found the duplicate. We had 2 period rows with the
exact same values. I deleted the entry with no foreign key values in
datavalue but when rerunning analytics we're getting a new error:
[image: Inline image 1]
Kind Regards,
Greg
On Fri, Feb 5, 2016 at 2:11 PM, Lars
In your datavalue table you will have references to the one you deleted.
Update those to point to the remaining one
On Feb 5, 2016 1:21 PM, "Greg Rowles" wrote:
> ps. 9295515 was the periodid (record) we deleted. The other duplicate
> periodid was 9295516...
>
> On Fri,
Hi Elmarie!
Interesting!
The mentioned incident and enrollment dates is available in the program rules,
with the syntax V{enrollment_date}, V{incident_date} and V{current_date}. See
table 30.3 for the full list of supported "variables":
Hi Markus,
Thanks for that info will look into it.
Yes I want to add a rule preventing capturing ie before 2015/04/01 and when a
user select a date before Error message appears forcing them to choose a
correct date.
But every year I need to move the date on by 1 year.
Regards,
Lars,
Thanks - true/false is noted for boolean.
But just to confirm re dates: WHY are you using dd.mm. for csv import
when all other dates in DHIS tend to be -mm-dd?
Regards
Calle
On 4 February 2016 at 16:04, Lars Helge Øverland
wrote:
> Hi Calle,
>
>
> On Thu,
Hi Ian,
Have you checked out our documentation?
http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/ch01s27.html
Regards,
Jason
On Fri, Feb 5, 2016 at 2:41 PM, Ian Manyama wrote:
> Hello team,
>
> Does DHIS 2 have API for fetching value of indicators?
>
> Regards,
>
Hi,
Hope all are well and ready for the weekend!
I've created an attribute of type date for use in tracker (v2.22). This
appears to be unable to accept future dates. Is this expected behaviour?
Cheers
Craig, NRC
___
Mailing list:
Hi all,
Viet Nguyen has joined our team as software developer.
Viet has 8 years of experience in Java software development in different
fields such as CMS systems, e-commerce and especially health-care. Viet has
in fact been working with HISP in a previous period in Vietnam and India,
developing
Hi Matt,
currently we do not support multi-tenancy. It is something we have been
considering for a while, but not implemented yet.
In source code speak, most meta-data objects are inheriting a shared object
(BaseIdentifiableObject) so adding a "Tenant" entity would not be a massive
task,
Hi Savita,
you should not get an exception, so please provide a bit more info (logs)
and we will have a look.
That said, in DHIS 2, almost all objects/tables might be linked to users,
so cleaning up all this is a complex task. You could simply disable the
user instead of deleting.
best regards,
Hi Hasina,
okay. Can you tell us which result you expect? Also please include log
output.
regards,
Lars
On Fri, Oct 30, 2015 at 1:35 PM, ramaso hasina
wrote:
> Hi all,
>
> I've created a program with some program stages.
> When I create a program indicator using the
revno: 21894
committer: Morten Olav Hansen
branch nick: dhis2
timestamp: Sat 2016-02-06 11:23:12 +0700
message:
minor bugfix
modified:
28 matches
Mail list logo