Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Morten Olav Hansen
Oh, and please make sure that you update the UIDs of these tables "default" also. Since you might want to to those on import also. So delete the duplicate default in those tables, but update the remaining default with the duplicate uid (hope that makes sense). -- Morten On Wed, Jul 15, 2015 at 1:

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Morten Olav Hansen
Yeah, I think that should be ok, just make sure you have a backup ;-) When it creates the default COC, it will also setup the tables around it, probably you will see duplicate "default" names in those tables also. -- Morten On Wed, Jul 15, 2015 at 1:43 PM, Mritunjay Dubey wrote: > Hey Mortan, >

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Hey Mortan, Thanx for your quick response. I tried deleting it from the table. But If I see it has FK references to following table. *categorycombos_optioncombos* *categoryoptioncombos_categoryoptions* *expressionoptioncombo* So before deleting that category-option-combo I need to delete refer

[Dhis2-devs] Using OU-Tree inside a DHIS2 App

2015-07-14 Thread Harsh Atal
Hi We are making a dhis2 App and have used the "ouwt.js" library for displaying the ou tree inside of our app. But for this a little change had to be made in the ouwt.js file. This is the change(marked in red):- . . 18 if (dhis2BaseUrl == undefined){ 19 var dhis2BaseUrl = ".."; 20 } 21 var organ

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Morten Olav Hansen
Hi You probably want to delete the "default" that was created during import, I assume no FK is attached to it. After you have done this, you should be able to change the UID of the other "default" COC to "dCWAvZ8hcrs". This is the way we have solved it a few places (before it was fixed in the cod

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Hello all, So as suggested I tried to update the "default" category-option-combo UID to the UID of source instance. But it didn't work. The reason was I already have a category-option-combo with same UID which also has name "default". I think which came after import. So now it has two "default" c

[Dhis2-devs] Problem with category option combo

2015-07-14 Thread Raheel Ayaz
Hi all, I have two categories Donor and Implementing partner with dimension type attribute merged together to a category combination "Donor & Implementing partner". When this category combination was defined so all the possible combinations were automatically created under category option combo.

Re: [Dhis2-devs] Internationalization of Web API response info / conflicts?

2015-07-14 Thread Alan Hill
Hi Mortenapologies for the delay in replying. I am still seeing this with /api/trackedEntityAttributes 2.20-SNAPSHOT Build revision: 19647 I will let you know if I encounter any others. Regards Alan On Wed, Jul 8, 2015 at 11:06 PM, Morten Olav Hansen wrote: > Hi > > In which endpoi

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19650: tracker-capture: apply the new webmessage reponse for registration, enrollment and event creation

2015-07-14 Thread noreply
revno: 19650 committer: Abyot Asalefew Gizaw branch nick: dhis2 timestamp: Tue 2015-07-14 21:05:51 +0200 message: tracker-capture: apply the new webmessage reponse for registration, enrollment and event creation modified: dhis-2/dh

[Dhis2-devs] [Bug 1474471] Re: Future dates allowed on report date at stage when using tracker capture

2015-07-14 Thread Abyot Asalefew Gizaw
Fix committed in trunk rev no. 19649. ** Changed in: dhis2 Assignee: (unassigned) => Abyot Asalefew Gizaw (abyot) ** Changed in: dhis2 Status: New => Fix Committed -- You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS. https

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19649: tracker-capture: disable future dates for event report date

2015-07-14 Thread noreply
revno: 19649 committer: Abyot Asalefew Gizaw branch nick: dhis2 timestamp: Tue 2015-07-14 20:32:32 +0200 message: tracker-capture: disable future dates for event report date modified: dhis-2/dhis-web/dhis-web-apps/src/main/webapp/dh

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19648: bug fix in validating zero during zero or positive integer data entry

2015-07-14 Thread noreply
revno: 19648 committer: Abyot Asalefew Gizaw branch nick: dhis2 timestamp: Tue 2015-07-14 20:31:13 +0200 message: bug fix in validating zero during zero or positive integer data entry modified: dhis-2/dhis-web/dhis-web-commons-resou

[Dhis2-devs] [Bug 1474471] [NEW] Future dates allowed on report date at stage when using tracker capture

2015-07-14 Thread Prosper BEHUMBIIZE
Public bug reported: The report date at stage, should not be allowing future dates. When you have a multiple stage program with registration, at the program stage data entry, the date of report should not allow future dates. This is happening with the tracker capture while individual records doesn

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19645: Program, translation

2015-07-14 Thread noreply
revno: 19645 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 17:02:21 +0200 message: Program, translation modified: dhis-2/dhis-web/dhis-web-maintenance/dhis-web-maintenance-program/src/main/resources/org

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19647: Including app title in error notifications for analytics and resource tables

2015-07-14 Thread noreply
revno: 19647 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 17:12:51 +0200 message: Including app title in error notifications for analytics and resource tables modified: dhis-2/dhis-services/dhis-servic

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19646: Removed optional labels in add/edit org unit

2015-07-14 Thread noreply
revno: 19646 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 17:09:01 +0200 message: Removed optional labels in add/edit org unit modified: dhis-2/dhis-web/dhis-web-maintenance/dhis-web-maintenance-organi

[Dhis2-devs] [Bug 1474419] [NEW] metadata import into empty db in 2.19 dhis2 fails

2015-07-14 Thread Rishi
Public bug reported: Dhis2 version: 2.19 tested: local and with the demo Sierra Leone server. OS: Local Windows 7, tomcat(-7.0.62) , postgres 9.4 browser: Firefox and Chrome. Problem statement Dhis2 version 2.19 fails to imports metadate into empty database. Goes fine with 2.18 version. How te

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19644: SQL view. Impl function for refreshing materalized views in list of sql views.

2015-07-14 Thread noreply
revno: 19644 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 16:50:19 +0200 message: SQL view. Impl function for refreshing materalized views in list of sql views. modified: dhis-2/dhis-api/src/main/java/o

Re: [Dhis2-devs] [Bug 1471276] [NEW] available selection of data elements and indicators in wrong language in version 2.19

2015-07-14 Thread Victor Garcia
Hi all, is there any news on this issue? Víctor On 3 July 2015 at 17:11, Rishi wrote: > Public bug reported: > > Dear all, > > Related to thread: https://lists.launchpad.net/dhis2-users/msg07563.html > > When making a new pivot table or graph using the data visualizer the > dataelements and ind

Re: [Dhis2-devs] Error Posting DataValueSet payload to DHIS2 via Web API

2015-07-14 Thread Lars Helge Øverland
Hi Farai, can you please look in the tomcat log and post errors? regards, Lars \ On Tue, Jul 14, 2015 at 3:31 PM, Farai Mutero wrote: > Hi All > > I'm trying to upload a dataValueSet payload to DHIS2. The payload > structure is as follows: > > { > >- "dataSet":"uokZhuVwx5F", >- "compl

[Dhis2-devs] Error Posting DataValueSet payload to DHIS2 via Web API

2015-07-14 Thread Farai Mutero
Hi All I'm trying to upload a dataValueSet payload to DHIS2. The payload structure is as follows: { - "dataSet":"uokZhuVwx5F", - "completeDate":"2014-06-29", - "period":"201406", - "orgUnit":"G4uL7kaWCqS", - "dataValues":[ 1. { - "dataElement":"N1p2C3w2X2u",

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Knut Staring
I meant 2.19 On Jul 14, 2015 2:47 PM, "Mritunjay Dubey" wrote: > Hey Knut, > > Upgrade means, Do I need to upgrade to 2.19, or somehow I can get a new > revision of 2.16 only. > > Please let me know. > > Thank you > > On Tue, Jul 14, 2015 at 6:08 PM, Knut Staring wrote: > >> It has been fixed. J

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19643: Time logging in data value import

2015-07-14 Thread noreply
revno: 19643 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 15:10:08 +0200 message: Time logging in data value import modified: dhis-2/dhis-services/dhis-service-dxf2/src/main/java/org/hisp/dhis/dxf2/dat

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Hey Knut, Upgrade means, Do I need to upgrade to 2.19, or somehow I can get a new revision of 2.16 only. Please let me know. Thank you On Tue, Jul 14, 2015 at 6:08 PM, Knut Staring wrote: > It has been fixed. Just upgrade. > On Jul 14, 2015 2:33 PM, "Mritunjay Dubey" > wrote: > >> Yes please

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Knut Staring
It has been fixed. Just upgrade. On Jul 14, 2015 2:33 PM, "Mritunjay Dubey" wrote: > Yes please fix it. > > Because it's hard to know the "default" category-combo-option UID, If you > don't have database access to source instance. > > Or If there is a way to get "default" category-combo-option U

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Yes please fix it. Because it's hard to know the "default" category-combo-option UID, If you don't have database access to source instance. Or If there is a way to get "default" category-combo-option UID please let me know. Thank you On Tue, Jul 14, 2015 at 4:30 PM, Morten Olav Hansen wrote

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19642: Analytics, adding support for specifying attribute option combo uids

2015-07-14 Thread noreply
revno: 19642 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 14:25:21 +0200 message: Analytics, adding support for specifying attribute option combo uids modified: dhis-2/dhis-api/src/main/java/org/hisp/dh

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19641: Analytics, added support for explicitly defining category option combo ids

2015-07-14 Thread noreply
revno: 19641 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 13:17:34 +0200 message: Analytics, added support for explicitly defining category option combo ids modified: dhis-2/dhis-services/dhis-service-

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Morten Olav Hansen
Yeah, I'm pretty sure this bug is still present in 2.16. Please try to fix it as Jason suggested.. -- Morten On Tue, Jul 14, 2015 at 5:47 PM, Alex Tumwesigye wrote: > Dear Dubey, > > Jason is right. > > I have had trouble before with a similar issue doing imports. > One thing I keep in mind whe

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Alex Tumwesigye
Dear Dubey, Jason is right. I have had trouble before with a similar issue doing imports. One thing I keep in mind when importing to a new instance (without using a database dump) is to overwrite the "default" category option combo with the one I am carrying from the existing data. To be safe, f

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Knut Staring
That would explain it, as 2.16 is a year old now... On Tue, Jul 14, 2015 at 12:32 PM, Mritunjay Dubey wrote: > Hey Jason, > > We are using DHIS 2.16 at both instances. > The build rev for source instance is *16594* and for destination instance > it is *16598*. > > Let me know if it is fixed. > T

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Hey Jason, We are using DHIS 2.16 at both instances. The build rev for source instance is *16594* and for destination instance it is *16598*. Let me know if it is fixed. Thank you On Tue, Jul 14, 2015 at 3:49 PM, Morten Olav Hansen wrote: > Could you also please provide your DHIS 2 version a

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Morten Olav Hansen
Could you also please provide your DHIS 2 version and build rev? we should have fixed this issue 1-2 months ago (or at least a similar issue) -- Morten On Tue, Jul 14, 2015 at 5:14 PM, Jason Pickering < jason.p.picker...@gmail.com> wrote: > In this case, you should probably alter the "default" c

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Jason Pickering
In this case, you should probably alter the "default" category option combo on the destination server to match that on the source server, if that is possible for you. Something like UPDATE categoryoptioncombo set uid = 'X' where categoryoptioncomboid = (SELECT categoryoptioncomboid from _

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
Hey Jason, Yes, I think it's "default" category option combo, but I'm not sure about it. I can see in UI of dataset, it shows as "default" and the date-created for category option combo is the date when I set-up the instance. So If it's a "default" *category-option-combo, *what should I do to syn

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19640: Moved jep functions from commons to support-system. Removed jep dependency from commons.

2015-07-14 Thread noreply
revno: 19640 committer: Lars Helge Overland branch nick: dhis2 timestamp: Tue 2015-07-14 11:47:47 +0200 message: Moved jep functions from commons to support-system. Removed jep dependency from commons. removed: dhis-2/dhis-support/

Re: [Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Jason Pickering
Does this happen to be the "default" category option combo? If so, it will be different between different instances of the database, and you will thus need to sync this one manually between your instances. Regards, Jason On Tue, Jul 14, 2015 at 11:43 AM, Mritunjay Dubey wrote: > > --

[Dhis2-devs] Fwd: Deployable war for previous builds

2015-07-14 Thread Mritunjay Dubey
-- Forwarded message -- From: Mritunjay Dubey Date: Tue, Jul 14, 2015 at 2:58 PM Subject: Re: [Dhis2-devs] Deployable war for previous builds To: Lars Helge Øverland Just adding to that We had selected every metadata other than *Validation-criteria & Report Table.* And while i

Re: [Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Bob Jolliffe
Hi Mritunjay As Lars says, if the categoryoptioncombos were not exported then that would indeed have caused a problem. And/or if you were using internal primary keys in your reports. But is there a particular reason you need to rely on the import/export functionality to do this? Did you try jus

Re: [Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Lars Helge Øverland
Another explanation is that the category option combos for some reason were not part of the exchange file, and was later re-generated in the destination system. This will give different UIDs. Let me know.. On Tue, Jul 14, 2015 at 10:47 AM, Lars Helge Øverland wrote: > Hi Mritunjay, > > are you r

Re: [Dhis2-devs] Problem to run validation rules

2015-07-14 Thread Knut Staring
Can you share your tomcat log? Knut On Jul 14, 2015 9:58 AM, "Salimone Domingos Nhancume" wrote: > Dear > > when trying to run Validation rule or click complete after entry data in > DHIS2 i am having the following error mensage: > > Sorry! The system failed to execute the operation. Usually, n

Re: [Dhis2-devs] Deployable war for previous builds

2015-07-14 Thread Lars Helge Øverland
Hi Mritunjay, are you referring the the internal database identifiers, or the UIDs (stable identifiers) ? The UIDs will (should) not change and this has nothing to do with the build. The database ids will likely change when you do an export followed by an import. When writing reports you should

[Dhis2-devs] [Branch ~dhis2-devs-core/dhis2/trunk] Rev 19639: moved MetaDataFilter files from commons.filter => common.filter, and removed package commons.filt...

2015-07-14 Thread noreply
revno: 19639 committer: Morten Olav Hansen branch nick: dhis2 timestamp: Tue 2015-07-14 14:33:21 +0700 message: moved MetaDataFilter files from commons.filter => common.filter, and removed package commons.filter (it seems these files

[Dhis2-devs] Problem to run validation rules

2015-07-14 Thread Salimone Domingos Nhancume
Dear when trying to run Validation rule or click complete after entry data in DHIS2 i am having the following error mensage: Sorry! The system failed to execute the operation. Usually, no data is lost and you can continue working by going back to the previous page. keeps coming up I am using DHI

[Dhis2-devs] [Bug 1474235] [NEW] Getting Exception when trying to get Phone Number in Event Reports

2015-07-14 Thread Neeraj
Public bug reported: Hello Developers, We are getting an exception when we are trying to get the 'Phone number' in Event Report. I am attaching the video to explain the problem for your reference. This is very important as our client need this information for calling. Please do the needful. *