Hi Halvdan
Thanks for the response. We are also testing the new importer functionality .
We have built metadata synchronisation which is leveraging the new importer
that got introduced in 2.23.
Apart from that, yes you are right and we understand that trunk can be OK
volatile state. But we
Hi,
As trunk is the development branch of DHIS2, the presence of bugs is to be
expected. In particular this last week we've had a few major ones which has
caused a range of breaking issues in the Maintenance app (among others).
That said, I've gone through your list. Some of the items I can
Hi Knut,
You are right, for instance when a user is picking a child to link to a
mother, there is a chance of linking that child to more than one mother,
there should be something to tell us that the child we are picking is
already linked to another mother. The MNCH program on the online demo is
Right, but if you are looking at a mother's dashboard and you want to link
the mother to a child, you are not getting any warnings that this child
already has a mother, I think?
The relationship functionality is really important, so certainly merits
more thinking, as you say.
Knut
On Fri, Jun
Hi,
We list all types of relationships that the TEI (the owner of the
dashboard) is linked to. The list also displays each relationship type.
The idea of implementing a warning is kind of redundant to me. The user has
kind of ignored what is already displayed and went to add another
Hi David,
I certainly understand the value of having this as an option, and I think
in general it would be nice to be able to (but not forced) to configure the
system to display a warning about preexisting relationships for that
particular TEI when the user creates a new relationship.
One
Hi Knut,
Thank you for you response. Looking at this outside the system, logically a
child cannot belong to more than one mother when both mothers are alive.
The system allows this to happen, another way of looking at it is when
people share names one would want to pick the correct child for each
Hi David,
Obviously, often you would want to have multiple relationships, e.g. a
mother often has more than one child. So I think what you are asking for is
a new functionality to be able to restrict some relationships to be of type
one-to-many, instead of many-to-many. You should probably write
Dear Morten,
Yes, I have the same issues but I wanted to clearly document them as a bug.
This happens when you extract the program metadata and then try to import
it to an existing similar program (same uid but in production).
The following fails to be imported correctly
- Option values are not
Hi Alex
Just to be clear, you are testing on /api/23/metadata or /api/24/metadata
endpoints? TW testing does not apply to legacy importer (available on
/api/metadata)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Fri, Jun 24, 2016 at 7:15 PM, Alex
Hi
I will try and look into these issues, please be aware that I have done a
lot of fixes to the importer in the last 2 days, so if this is from before
that.. probably you need to re-test.
Will go over them on Monday and see what can be fixed for release.
--
Morten Olav Hansen
Senior Engineer,
For the record, this was fixed.
Lars
On Mon, Mar 14, 2016 at 8:57 AM, Archana Chillala wrote:
> Currently using DHIS version 2.23 on both instances.
>
> Archana Chillala
> Application Developer
> Email archa...@thoughtworks.com
> Telephone +91 9100960533
Hi Aamer,
I see. These issues are hard for us to debug without additional info. Can
you reproduce on the demo server?
If not, can you produce all info about your chart, tomcat log, js developer
console output, DHIS 2 version ?
regards,
Lars
On Fri, Apr 29, 2016 at 3:57 PM, Aamer Mohammed
On Fri, Jun 24, 2016 at 12:10 PM, Archana Chillala <
archa...@thoughtworks.com> wrote:
> Thank you, Lars.
>
> I am able to reproduce the issues on the dev instance as well. 'Yes Only'
> (and most other value types are rendered as blank fields)
>
>
> [image: Inline image 1]
>
> Also, based on the
Thank you, Lars.
I am able to reproduce the issues on the dev instance as well. 'Yes Only'
(and most other value types are rendered as blank fields)
[image: Inline image 1]
Also, based on the '*value type*' of the Attribute, some attributes show up
in the new Data Sets module (in maintenance
Hi Sri,
right, we will add that.
regards,
Lars
On Fri, Jun 24, 2016 at 9:41 AM, Srikanth Katta
wrote:
> Hi,
>
> We want to use event reports and event charts plugins. We had
> documentation regarding charts and report tables but we didn't find the any
>
Hi Archana,
thanks for the feedback.
Did you test against
On Fri, Jun 24, 2016 at 10:01 AM, Archana Chillala <
archa...@thoughtworks.com> wrote:
> Hi,
>
> We have created an attribute with a value type - "Yes Only" and assigned
> it to data set. In the maintenance app, when we look at the data
Hi,
We want to use event reports and event charts plugins. We had documentation
regarding charts and report tables but we didn't find the any documentation
for event reports and event charts how to use them in our application. Can
you point us the documentation for this.
Thanks,
Srikanth Katta.
Thank you Morten. Will explore this and revert.
Sent from my BlackBerry 10 smartphone.
Original Message
From: Morten Olav Hansen
Sent: Friday, 24 June 2016 00:35
To: dhis2-devs@lists.launchpad.net
Reply To: Bug 1538443
Subject: Re: [Dhis2-devs] [Bug 1538443] Re: Metadata import of users fails
On Fri, Jun 24, 2016 at 4:56 AM, Pramil Liyanage wrote:
> Hi Lars,
>
> In that case, what happens to the blank space? Any method to use it in
> default forms? Like by having two columns for elements?
>
>
Hi Pramil,
I would say some blank space is not a problem, and also you
Hi Devs,
Are there any plans to address the issue below like issuing a warning
message when someone tries to link a record in a relation ship thats
already linked to another?
rgds
David
On 23 Jun 2016 20:50, "David Muturi" wrote:
> Hi Devs,
> I have noticed that it is
21 matches
Mail list logo