dhis2-users team mailing list archive

[Neeraj Gupta <neeraj.hisp@xxxxxxxxx>]

Hi Elmarie,
Thanks for the clarification but no, in my case the attributes which are
creating the problem are not part of the Tracked entity.

On Wed, Oct 24, 2018 at 5:42 PM Elmarie Claasen <elmarie@xxxxxxxx> wrote:

> Hi Neeraj,
>
>
>
> These attributes that you refer to are they part of the Tracked Entity
> defined? My understanding which may be wrong is if you define certain
> attributes as part of the tracked entity e.g. Person then those attributes
> would be mandatory in the programs.
>
>
>
> Regards,
>
>
>
> *Elmarie Claasen*
>
> [image: Hisp logo]
>
> Project Manager
>
> Health Information Systems Program
>
> Tel:      041-367 1027
>
> Cell:     082 374 2209
>
> E-mail: elmarie@xxxxxxxx
>
> Skype:  elmarie.claasen52
>
>
>
> *From:* Dhis2-devs <dhis2-devs-bounces+elmarie=
> hisp.org@xxxxxxxxxxxxxxxxxxx> *On Behalf Of *Neeraj Gupta
> *Sent:* Wednesday, October 24, 2018 9:34 AM
> *To:* DHIS 2 Users list <dhis2-users@xxxxxxxxxxxxxxxxxxx>; DHIS 2
> developers <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
> *Subject:* [Dhis2-devs] Mandatory attributes can not be made optional
>
>
>
> Dear All,
>
>
>
> Once the attribute is made mandatory and if at a later stage it is
> considered to be optional then we are able to go to attributes of the
> program and uncheck the mandatory field but this is not reflected in the
> registration page.
> It always treats the attribute as mandatory, the user cannot move forward
> without entering data for those attributes.
>
>
>
> Version: 2.30
> Build revision: bd6e33e
>
> Build date: 2018-10-23 02:06
>
>
>
> --
>
> Thanks,
> Neeraj Gupta
>
> *This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer
> <http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclaimer@xxxxxxxx
> <disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>


-- 
Thanks,
Neeraj Gupta