dhis2-users team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Good. Blueprint for 2.15 here.

https://blueprints.launchpad.net/dhis2/+spec/sortable-trackedentity-attribute-options


On Fri, Jan 24, 2014 at 12:43 PM, Rodolfo Melia <rmelia@xxxxxxxxxxxx> wrote:

> I think that the proposed solution covers all cases - having the
> possibility of making 'null/ blank' the default option is something that
> will be required in many cases.
>
> *Rodolfo Meliá*
> *Principal  |  *rmelia@xxxxxxxxxxxx
> Skype: rod.melia  |  +44 777 576 4090  |  +1 708 872 7636
> www.knowming.com
>
>
> On Fri, Jan 24, 2014 at 9:47 AM, Lars Helge Øverland <larshelge@xxxxxxxxx>wrote:
>
>>
>>
>>
>> On Thu, Jan 23, 2014 at 9:36 PM, Jose Garcia Muñoz <josemp10@xxxxxxxxx>wrote:
>>
>>>
>>> Many thanks Lars,
>>>
>>>
>>>>
>>>> Let me ask: are default values something you foresee to be needing for
>>>> all kinds of attributes, not just the predefined value-type?
>>>>
>>>
>>> Honestly, It is difficult to think in an specific example that would
>>> need a default value for other kind of attributes (different to the
>>> predefined ones). Well, I don´t know, maybe could be a nice feature to
>>> implement but I don´t think is going to be really  useful in the 95% of the
>>> cases...
>>>
>>
>>
>> Okay thanks. Could a good-enough solution be to
>>
>> - implement ordering of options
>> - have the first option be the displayed/selected by default
>> - allow for putting a blank/null value at the first index of the
>> predefined options?
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>