[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18477: ER css fixes.

Merge authors: Jan Henrik Øverland (janhenrik-overland) revno: 18477 [merge] committer: Jan Henrik Overland janhenrik.overl...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 17:18:59 +0100 message: ER css fixes. modified:

[Dhis2-devs] Events capture not loading

Hi, I am having hard time loading event capture on the new instance on server. The system normally works fine on another server running 2.17 but when i restore the back up to another server, all other functions (event report, pivot report, reports, data entry etc) are working fine excluding event

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18478: Analytics. Checking if dynamic dimensions in request are defined as data dimensions, to avoid fai...

revno: 18478 committer: Lars Helge Overland larshe...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 17:26:17 +0100 message: Analytics. Checking if dynamic dimensions in request are defined as data dimensions, to avoid failed

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18479: Analytics. Inserting all dimension items explicitly when no items are selected for a dimension.

revno: 18479 committer: Lars Helge Overland larshe...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 18:49:02 +0100 message: Analytics. Inserting all dimension items explicitly when no items are selected for a dimension.

Re: [Dhis2-devs] Events capture not loading

Hi, I suspect this is related to caching. What happens if you do full browser cache cleaning? - Thank you, Abyot. (sent from mobile) On Mar 4, 2015 5:44 PM, Kamugunga Adolphe kaa...@gmail.com wrote: Hi, I am having hard time loading event capture on the new instance on server. The

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18482: Removed maven.dhis2.org repository. Added smslib repository.

revno: 18482 committer: Lars Helge Overland larshe...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 22:41:38 +0100 message: Removed maven.dhis2.org repository. Added smslib repository. modified: dhis-2/pom.xml -- lp:dhis2

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18481: Script

revno: 18481 committer: Lars Helge Overland larshe...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 22:09:59 +0100 message: Script modified: dhis-2/dhis-api/src/main/java/org/hisp/dhis/dataset/Section.java

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18480: Analytics. Better implementation of max records limit, which breaks the query response rather tha...

revno: 18480 committer: Lars Helge Overland larshe...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 19:36:19 +0100 message: Analytics. Better implementation of max records limit, which breaks the query response rather than

Re: [Dhis2-devs] Code build error 2.18

Hi Paul, this is now fixed. We have moved some libraries to maven central and gotten out of the maven repository business. regards, Lars ___ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe :

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18483: use CollectionPersister to set manyToMany/oneToMany properties on Property class

revno: 18483 committer: Morten Olav Hansen morte...@gmail.com branch nick: dhis2 timestamp: Thu 2015-03-05 11:09:14 +0700 message: use CollectionPersister to set manyToMany/oneToMany properties on Property class modified:

Re: [Dhis2-devs] Events capture not loading

I tried both clearing browser and system caches but it doesn't resolve the it. The issue is that when i browser the a copy of this instance hosted somewhere else where i took the backup to restore it is is working fine. On 4 March 2015 at 20:17, Abyot Gizaw aby...@gmail.com wrote: Hi, I

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

One issue that is there with making the user able to see the TEI data at any orgunit is of confidentiality. Because with this approach the user at district1 (which let's say handles TB programs) can see the TEIs at district2(which handles HIV data).This can be a big issue with private data like

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

Hi Harsh, Do you really want to migrate? Or you want to register data in another org unit? - Thank you, Abyot. (sent from mobile) On Mar 4, 2015 9:07 AM, Morten Olav Hansen morte...@gmail.com wrote: Hi Harsh You are not allowed to update the orgUnit pointer, this was supposed to be the

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

thanks morten ,I thought it was a bug @abyot I want to migrate the tracked entity instance into another organisation unit. So when the next time i select the orgunit from which i migrated i dont want to see the tracked instance there but instead it has to come up in the new org unit.

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

Hi Harsh You are not allowed to update the orgUnit pointer, this was supposed to be the point of registration.. and was thought of as being read-only after initial registration. That said, I'm 90% sure we are changing this for 2.19, we are having discussion about that now (we would rather have

Re: [Dhis2-devs-core] org unit association from TEI to enrollment

We already have a blueprint on this [1], I can take on the job of changing the web-api (require orgUnit in enrollment, and remove orgUnit from trackedEntityInstance), if someone else can take care of SQL upgrade.. that would be good, since its not really what I'm good at.. I guess we should

[Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

Dear All I am trying to shift a trackedentityinstance from one organisationunit to another. For this i tried to use the web API resource for the updation of trackedEntityInstance. This ,i have found, is not working for the organisationunit as it is not changed while the changes in other

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

Ok, you know what your needs are. Are you also going to migrate events? What will happen to already submitted/acted report? You need to carefully look into the migration requirement. I am strongly against the idea of migration. With migration, you will lose information. If it is possible to

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18473: minor change, add new supported date format in DateUtils (including ms)

revno: 18473 committer: Morten Olav Hansen morte...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 16:47:54 +0700 message: minor change, add new supported date format in DateUtils (including ms) modified:

[Dhis2-devs] Code build error 2.18

Hello, can anyone help me solve this error, I wm building dhis2 2.18 code , I m running this command : I m using mvn clean -Dmaven.test.skip=true install [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:35 min [INFO]

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18474: applied patch from TW, adds full date+time info when exporting data values

revno: 18474 committer: Morten Olav Hansen morte...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 17:13:19 +0700 message: applied patch from TW, adds full date+time info when exporting data values modified:

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

I agree. What we are doing is having a placeholder org unit for the TEI, and then registering the events against the actual org unit. Then the event reports and aggregations work against the event org unit . This makes it easy (possible!) to look the TEI up as you will always know the org unit

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

By migration I meant the same feature as 'change location' in individual records. Now, as abyot said if it is possible to access a TEI at any org unit and enter data for any org unit then that is one way to do it but its not the same as 'change location' in individual records. The need for

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 18475: tracker|event-capture: capture coordiante - WIP

revno: 18475 committer: Abyot Asalefew Gizaw aby...@gmail.com branch nick: dhis2 timestamp: Wed 2015-03-04 12:34:55 +0100 message: tracker|event-capture: capture coordiante - WIP removed:

Re: [Dhis2-devs] [trunk]Issue in trackedEntityInstance updation through web API

I see your point. But, the situation that you have referred a patient from orgunit A to orgunit B does not change the fact that the patient was registered/enrolled at orgunit A. By doing migration, we are destroying this information which for me is wrong. What we need to probably do is provide a

Re: [Dhis2-devs-core] org unit association from TEI to enrollment

Okay. I can do the SQL updgrade, just tell me about what database columns/tables will change, and let Abyot know about the API changes. On Wed, Mar 4, 2015 at 9:04 AM, Morten Olav Hansen morte...@gmail.com wrote: We already have a blueprint on this [1], I can take on the job of changing the

[Dhis2-devs] BUG(s) - Data Element Group Editor

Hi Just picked up a significant bug in the Data Element Group Editor: 1. Open DEG editor, and select a DE group with existing members. 2. If required, filter the list of available elements. 3. First bug: data elements that already ARE group members are not excluded from the available list. 4.