Thanks Abyot ! - will test and get back to you if we have any problems.
*Rodolfo Meliá*
*Principal | *rme...@knowming.com
Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636
www.knowming.com
On 12 June 2016 at 13:09, Abyot Asalefew Gizaw wrote:
> Hi,
>
> A fix is committed for this. Rev
Fantastic! Many thanks Abyot
On Sun, Jun 12, 2016 at 2:09 PM, Abyot Asalefew Gizaw
wrote:
> Hi,
>
> A fix is committed for this. Rev. 22063 and above should work...
>
> --
> Abyot A. Gizaw.
> Senior Engineer, DHIS2
> University of Oslo
> http://www.dhis2.org
>
> On Fri, Jun 10, 2016 at 1:44 PM,
Hi,
A fix is committed for this. Rev. 22063 and above should work...
--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org
On Fri, Jun 10, 2016 at 1:44 PM, Rodolfo Melia wrote:
> Look forward to check the next 2.22 build with the updated feature. Please
> let us kno
Look forward to check the next 2.22 build with the updated feature. Please
let us know from what 2.22 build we can start testing.
*Rodolfo Meliá*
*Principal | *rme...@knowming.com
Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636
www.knowming.com
On 10 June 2016 at 07:56, Lars Helge Øve
Hi there,
seems we agree, just wanted to add that we should always trim blank values
to null before storing, and nulls are not in conflict with uniqueness.
Lars
On Fri, Jun 10, 2016 at 7:29 AM, Abyot Asalefew Gizaw
wrote:
> Hi,
>
> I think I missed that it was not required from the server sid
Hi,
I think I missed that it was not required from the server side api ... it
is easy to fix from the client side.
--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org
On Fri, Jun 10, 2016 at 4:59 AM, Jose Garcia Muñoz
wrote:
>
> Hi guys,
>
> any agreements on this
Hi guys,
any agreements on this? :)
I would like to know if I need to change the configuration of some
programs (unique attributes are always compulsory) or not (unique
attributes can be optional). I would prefer if we can keep them blank as
well (so they are optional).
Thanks
Jose
On Wed, Ju
I just want to support the idea that blanks should be accepted and not
checked for uniqueness. I'm glad to hear that the API already supports
this, so it will be great if the UI follows that logic.
*Rodolfo *
On 8 June 2016 at 10:49, Juan Manuel Alcantara Acosta <
jmalcanta...@gmail.com> wrote:
Hi Markus
I had a short email exchange with Abyot last week and he said the same "So many
blanks can not be unique” but for a value to be unique there must be a value.
If the database and the API do not have this requirement, the interface should
follow the program’s configuration.
Best regards,
Hi guys!
Chiming in - I think Abyot is on leave today.
This seems to be a discrepancy that we should just resolve one way or the
other. You might say that a blank value is not unique, but I have also recently
encountered a use case where we needed a non-compulsory unique attribute like
you Jose.
Hi
Sorry for late reply, but I have been looking into this, and from the
backend this is not required. I'm adding in Abyot, hopefully he can answer
why it is required in the UI part (I see it's marked with red star, and it
will not allow it without a value)
--
Morten Olav Hansen
Senior Engineer,
Dear devs,
we realized that tracked attributes are always compulsory even if they are
not marked like that in the program definition? so it is not possible at
all to keep them blank using the Tracker Capture.
In PSI (and I guess is the same for many different countries), we need to
define unique
12 matches
Mail list logo
