Hi
I think most of these issues should have been resolved now, please try it
again...
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, Nov 7, 2016 at 8:09 AM, Morten Olav Hansen wrote:
> Hi Archana
>
> I'm sorry I've been trying
This should have been fixed now, please try it out and report back to us
(give our servers 30+ min to build a new war file)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, Nov 7, 2016 at 12:39 PM, Morten Olav Hansen
wrote:
>
Hi, I tried both with /api/metadata and the UI.
Olav
> 7. nov. 2016 kl. 07.07 skrev Morten Olav Hansen :
>
> Hi Olav
>
> Which endpoint did you use for this? /api/metadata or /api/24/metadata? (or
> did you just use the UI)
>
> --
> Morten Olav Hansen
> Senior Engineer,
Thank you Calle and Jim for your quick response,
Let me try it i will be back to you shortly,
Regards,
Adolphe
*Adolphe Kamugunga*
*MIS Technical Advisor*
Mobile: +250 788 740 578
Email:kaa...@gmail.com
Skype: ka.adolphe
RWANDA
On 4 November 2016 at 18:02, Jim Grace wrote:
Hi Olav
Which endpoint did you use for this? /api/metadata or /api/24/metadata? (or
did you just use the UI)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Fri, Nov 4, 2016 at 3:59 PM, Olav Poppe wrote:
> Hi devs,
> I’m trying to
Yeah, this is probably related to the same issues we are already
investigating.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Mon, Nov 7, 2016 at 12:32 PM, Aamer Mohammed
wrote:
> Hi,
>
> As per the logs, metadata sync is
Hi,
As per the logs, metadata sync is failing in the importer phase when trying
to import metadata.
--
* ERROR 2016-10-24 11:44:03,758 Exception occurred while trying to import
the metadata. object references an unsaved transient instance - save the
transient instance before flushing:
Okay. Thanks for the information, Lars.
Archana Chillala
Application Developer
Email archa...@thoughtworks.com
Telephone +91 9100960533 <+91+9100960533>
[image: ThoughtWorks]
This should be fixed in 2.25/master now.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Fri, Nov 4, 2016 at 11:45 PM, Jim Grace wrote:
> This has recently been noticed and reported as a new bug at
>
Hi Archana
Seems to work fine on the play/demo server, but maybe you have a certain
config that doesn't work.
Can you try and reproduce on [1] and give us the steps back?
[1] https://play.dhis2.org/demo (admin/district)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
>
> *1) Translations* are not getting synced.
> In previous versions, translations used to sync. But, looks like
> that's not the case with 2.25. It affects all metadata objects that are
> translatable.
>
I assume this is the same in 2.24? have you verified that the translations
are actually
Hi Archana
I'm sorry I've been trying to reproduce this for a while now, but I have
not been able to. Are you importing these into a fresh database? or does it
already contain some metadata?
Are you able to share the database/payload where this is happening?
--
Morten Olav Hansen
Senior
Yes. the annotation was something new in 225.
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1638551
Title:
Category option group set should be optional for approval level
Status in DHIS:
Fix
It worked already in 2.24 and earlier. It was just a problem in 2.25 and
trunk.
On Sun, Nov 6, 2016 at 5:19 PM, Lars Helge Øverland wrote:
> Great. Can we back-port to 2.24 as well?
>
>
> On Sun, Nov 6, 2016 at 6:52 AM, Morten Olav Hansen <
> 1638...@bugs.launchpad.net> wrote:
Great. Can we back-port to 2.24 as well?
On Sun, Nov 6, 2016 at 6:52 AM, Morten Olav Hansen <
1638...@bugs.launchpad.net> wrote:
> Should be fixed in 2.25 and master. This was happening due to non-
> standard property mapping for dataApprovalLevel (which our schema
> introspector didn't
Great, thanks!
On Sun, Nov 6, 2016 at 1:52 AM, Morten Olav Hansen <
1638...@bugs.launchpad.net> wrote:
> Should be fixed in 2.25 and master. This was happening due to non-
> standard property mapping for dataApprovalLevel (which our schema
> introspector didn't understand). So it was overriden
Should be fixed in 2.25 and master. This was happening due to non-
standard property mapping for dataApprovalLevel (which our schema
introspector didn't understand). So it was overriden with annotation
(@Property), it might have been a bit strict. Relaxed it down to not
required now.
** Changed
17 matches
Mail list logo