Hibernate exception should now be caught, and a web message sent back,
please try it out. Also added a new default exception handler, which
unwraps the message and sends back to the user (full stack trace is still
available on the server).
@Paulo: deletions -should- be allowed... but I don't think
Hi
Could you show me the payload you are sending? this API is in use by
several clients without any issues.
Also, it says `Unrecognized field "programInstance"` are you sure this is
really related to `@JsonIgnore` on the `Coordinate` class?
It would be easier to debug if you can share the event
Hi Juma
>From 2.18 to 2.23 there have been quite a large number of changes. For your
exact issue, it is related to the fact that organisation unit feature type
was changed from a simple string, to a set of pre-defined constants.
In the particular case you have here, you need to change `Polygon` t
Hello Adolphe,
Such a scenario is currently working and being tested for the Android
Tracker capture app. Perhaps you can try the app, that is if you haven't
already. It has a feature to search from another facility.
Regards,
Ranga
On 14 Jun 2016 13:03, "Kamugunga Adolphe" wrote:
Hi,
We are ru
I did backport to 22. Did you test it there? Same error?
On Jun 15, 2016 7:19 PM, "Blake Hansen" wrote:
> Hi Lars, this is still an issue it seems. Any chance of backporting?
> Many thanks.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bu
Hi
Please advise how can I export metadata from 2.18 and import to 2.23. The error
i get is:
Caused by: com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not
construct instance of org.hisp.dhis.organisationunit.FeatureType from String
value 'Polygon': value not one of declared Enum
Hi Lars, this is still an issue it seems. Any chance of backporting?
Many thanks.
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1557996
Title:
cannot-replicate-user-2.22
Status in DHIS:
Fix C
Hi Lars, sorry for delay in reply yes exactly, in the pivot app.
Cheers, Dave
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1592439
Title:
Adding all program indicators to a report at once d
Hi,
this is now fixed in 2.23 and trunk version
.
regards,
Lars
On Tue, May 3, 2016 at 10:44 PM, Nicola Hobby wrote:
> Hi Matt,
> Turns out this bug was fixed and when we upgrade to 2.23 it will be
> resolved or update the version of 2.22 in the meantime.
> Thanks,
> Nicola
>
> On Tue, May 3,
Thanks, great.
On Wed, Jun 15, 2016 at 3:05 PM, Vanya Seth wrote:
> Hi Lars
>
> We will make that change.
>
> Regards
> Vanya
>
> On Wed, Jun 15, 2016 at 2:37 PM, Lars Helge Øverland
> wrote:
>
>>
>> Hi Vanya,
>>
>> I understand your concerns here.
>>
>> However this is fine with me - this logg
Hi Lars
We will make that change.
Regards
Vanya
On Wed, Jun 15, 2016 at 2:37 PM, Lars Helge Øverland wrote:
>
> Hi Vanya,
>
> I understand your concerns here.
>
> However this is fine with me - this logging is not visible to users and
> there won't even be produced a log file if the sync isn't
Thanks Araz, crystal clear. So, waiting for 2.24 :)
Thanks
On Tue, Jun 14, 2016 at 10:09 AM, Araz Abishov wrote:
> Hi Jose and Morten,
>
> Since we are relying on display[*] properties in SDK and android apps, we
> will get translations as soon as api support will be there (if you are
> running
Dear Devs,
I don't know if I am doing something wrong, but I can not update
dataelements using a CSV import through the web interface (Strategy
selected is New and Updates). Just copying here a simple example, where we
have: name, uid (of a dataelement that currently exists), code (empty), and
s
Hi Morten,
This is still looking for other 2 properties to map while deserializing, we
are getting exception like
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException:
Unrecognized field "programInstance" (class
org.hisp.dhis.dxf2.events.event.Event), not marked as ignorable (22 known
Hi Devs
We are trying to work with new DHIS2 instance on a laptop and the first thing
we have done was to install the DHIS2 Live. It loads quite alright and we have
exported some already exisiting meta-data from a working instance to so that we
can start working on org units and other resources
Hi Devs
We are trying to work with new DHIS2 instance on a laptop and the first thing
we have done was to install the DHIS2 Live. It loads quite alright and we have
exported some already exisiting meta-data from a working instance to so that we
can start working on org units and other resourc
Hi Lars,
Following up on this discussion - has there been any review of the current
limitation?
Thanks.
Regards,
Dapo Adejumo
> On 16 Mar 2016, at 18:04, Elmarie Claasen wrote:
>
> Hi all,
>
> We also had this issue once. Maybe one should then get a warning when you add
> >200 users to Userg
Thanks Lars
On Wed, Jun 15, 2016 at 12:34 PM, Lars Helge Øverland
wrote:
> I have created an issue here:
>
> https://github.com/dhis2/maintenance-app/issues/184
>
> Lars
>
>
> On Wed, Jun 15, 2016 at 10:09 AM, Prosper BT wrote:
>
>> Thanks Knut,
>>
>> We weren't even thinking about resolution s
I have created an issue here:
https://github.com/dhis2/maintenance-app/issues/184
Lars
On Wed, Jun 15, 2016 at 10:09 AM, Prosper BT wrote:
> Thanks Knut,
>
> We weren't even thinking about resolution since we were only dealing with
> data elements, but I guess the developers need to do someth
Hi David,
On Wed, Jun 15, 2016 at 9:45 AM, David Siang Fong Oh
wrote:
> Just my two cents on API versioning:
>
>- I agree that it's good practice to retire API versions. Maintaining
>too many older versions is costly. The question is how many old versions to
>support.
>- API vers
Hi Vanya,
I understand your concerns here.
However this is fine with me - this logging is not visible to users and
there won't even be produced a log file if the sync isn't enabled, so I'm
fine with you adding a new logger to Log4JLogConfigInitializer. Let me know
what you think.
best regards,
Thanks for Sharing Muhammad ! = EKANI Guy
MOPH Cameroon
Le Mercredi 15 juin 2016 9h38, Mohammad Ullah a écrit
:
Hello Morten,
Yes these steps are for transferring dataset from 2.19 version to 2.22.
On Wed, Jun 15, 2016 at 12:53 PM, Morten Olav Hansen wro
Hello Morten,
Yes these steps are for transferring dataset from 2.19 version to 2.22.
On Wed, Jun 15, 2016 at 12:53 PM, Morten Olav Hansen
wrote:
> Hi
>
> I see you are changing some properties, I guess this is moving from one
> version of DHIS to another version?
>
> If you are using 2.23 or n
Thanks Knut,
We weren't even thinking about resolution since we were only dealing with
data elements, but I guess the developers need to do something about it.
But also is duplication reported by Shivan a bug or intended to be so?
Regards
On Wed, Jun 15, 2016 at 11:02 AM, Knut Staring wrote:
Hi Prosper,
I have encountered the same problem, and it is very annoying.
It is still there, but too far down, so that with many resolutions you it
is outside the screen. I think it should be moved up to replace the
compulsory description, which I am not sure is needed at all.
Knut
On Wed, Jun
Just my two cents on API versioning:
- I agree that it's good practice to retire API versions. Maintaining
too many older versions is costly. The question is how many old versions to
support.
- API versioning should allow application developers to upgrade their
DHIS2 server without
Hi Lars
The metadata versioning and sync is an optional feature. It totally depends
on the deployment strategy that we want to adopt and given that whether we
choose to do metadata sync or not.
For these reasons adding the metadata sync log as a first class citizen to
the Log4JLogConfigInitialize
Hi Vanya,
retiring API versions is what most vendors do. There is a balance between
the cost of maintaining old versions vs producing new features and
providing a modern application. We know that things inevitably change over
time due to needs from users.
The API versioning is meant to provide a
Hi there,
okay. It would be great if we do not introduce another way of doing
logging. The problem is that resolving the DHIS2_HOME directory is a bit
complex - the system looks for the system property dhis2.home, the env
variable DHIS2_HOME, then falls back to opt/dhis2. log4j 1 does not support
Dear team,
Previously whenever you selected a data element(a) to use as numerator or
denominator the name(s)/formula if applied would display in the lower part
of the edit box but now it doesn't not show making it very difficult to
cross check after selection and editing there after.
Also the "va
30 matches
Mail list logo
