Re: [Dhis2-devs] Upgrading DHIS2 from 2.21 to 2.24 and using new exporter/importer

Hi Aamer Probably what is happening is that the new database has some constraints that the old one doesn't. We have had some issues with hibernate in the past, and for certain databases that means that many of the constraints was not applied.. If you look at the messages, you will see that e.g

[Dhis2-devs] Error in DHIS2

Dear Team, When i am trying to open the dhis2 software in web browser. It shows the following error. How to rectify it? : org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is

Re: [Dhis2-devs] Upgrading DHIS2 from 2.21 to 2.24 and using new exporter/importer

Any thoughts please on the below approach. Let us know if any details are required from our end around this. On Wed, Aug 17, 2016 at 1:18 PM, Aamer Mohammed wrote: > Hi Morten, > > We have our metadata configured on a DHIS 2.21 instance. We have > sequentially upgraded

[Dhis2-devs] [Bug 1614543] Re: Dry run Alters Data 2.23

Regarding the logic for object matching, it's a bit confusing in the old importer.. it goes something like this 1) Try to match on UID 2) Try to match on CODE 3) If name == unique, match on NAME 4) if object is orgUnit, also try to match on UUID This has changed in the new importer, where we

[Dhis2-devs] [Bug 1614543] Re: Dry run Alters Data 2.23

Hi, I will look at this bug. Just know that in 2.23 (if you can go the web- api route) we also have a new importer located at /api/23/metadata, which does a much much better job at these kinds of things. ** Changed in: dhis2 Status: New => Confirmed -- You received this bug notification

[Dhis2-devs] Response differences between /api/metadata and /api/23/metadata

Hi, I am working on updating our applications to DHIS 2 v 2.23 specifically in regards to upgrading to using the /api/23/metadata api call. I am testing against revision 23053. We have a few issues: 1. Is there any documentation outlining the response structure from all API calls,

Re: [Dhis2-devs] [Bug 1614956] Re: Dataset Import/Export does not affect custom entry form

You need this 1) in data set, refer to the uid only, dataEntryForm: { id: "id123" } Thats it.. there was an issue with what we call the "internal merge strategy", basically we missed something when we converted dataEntryForm from an "normal" object to be an id object @Abyot -- Morten Olav

[Dhis2-devs] GSoC '16 contribution

Hello devs, I have developed a ReactJs app for quick entry of Tracker Capture data under the Google Summer of Code program. I'd like to share the details of the app and how it will help the community. This is the link to the source code . *The

Re: [Dhis2-devs] [Bug 1614956] Re: Dataset Import/Export does not affect custom entry form

Thanks Morten, testing now, Can you let me know where the should live? Does it need to be in there twice, or just the once underneath the tag? like this: [image: Inline image 1] and [image: Inline image 2] *Timothy Harding* Sr. Systems Analyst, BAO Systems +1 202-536-1541 |

Re: [Dhis2-devs] scheduling in DHIS

Vanya, If you're talking about simply exposing TaskExecutor.submitListenable(Runnable) in the Scheduler interface, it's not a big deal. I'd think you could just go ahead. Alternately you could wire the AsyncListenableTaskExecutor bean directly into the service, I suppose. On Mon, Aug 22, 2016 at

Re: [Dhis2-devs] scheduling in DHIS

Hi Lars Any comments on this one? Regards Vanya On Wed, Aug 17, 2016 at 12:44 PM, Vanya Seth wrote: > Hi Lars > > We are looking at extending org.hisp.dhis.system.scheduling.Scheduler to > also have the ability to return the ListenableFuture for a Runnable as > well.

[Dhis2-devs] [Bug 1614956] Re: Dataset Import/Export does not affect custom entry form

This should now be fixed in latest 2.23 and up ** Changed in: dhis2 Status: Confirmed => Fix Committed ** Changed in: dhis2 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS.

[Dhis2-devs] [Bug 1614956] Re: Dataset Import/Export does not affect custom entry form

** Changed in: dhis2 Status: New => Confirmed -- You received this bug notification because you are a member of DHIS 2 developers, which is subscribed to DHIS. https://bugs.launchpad.net/bugs/1614956 Title: Dataset Import/Export does not affect custom entry form Status in DHIS:

Re: [Dhis2-devs] [Dhis2-users] Read only field on custom form

Dear Elmarie, Please try Alex On Sun, Aug 21, 2016 at 11:27 PM, Elmarie Claasen wrote: > Hi all, > > > > I am using 2.23 revision 23051 2016-08-03 17:41 > > > > I have a custom form for which I want data element value to be read-only. > > > > I have tried various ways but