dhis2-devs team mailing list archive

[Morten Olav Hansen <mortenoh@xxxxxxxxx>]

Hi

Please remember that the way we handle options/optionSets have been changed
now. You need to have <options> <option code="codea" name="Option A" />
</options> <optionSets> <optionSet> <options><option code="codea" />
</options> </optionSets>

This now works as any other metadata... you first define the options, then
create optionsets with references to these options.. this allow for option
reuse, and also translation

--
Morten

On Fri, Nov 28, 2014 at 4:28 PM, Mansi Singhal <msinghal@xxxxxxxxxxxxxxxx>
wrote:

>
> Hello Lars,
>
> We are trying to create 'options' and 'optionSets' on empty Database.
>
> Request Payload:
>
> {
>     "optionSets": [{
>         "id": "b73cdddd773",
>         "name": "Hours",
>         "options": [{
>             "code": "b64365ac185",
>             "id": "b64365ac185",
>             "name": "One"
>         }]
>     }, {
>         "id": "b640fd0cc0f",
>         "name": "Minutes",
>         "options": [{
>             "code": "b65ad0e22c5",
>             "id": "b65ad0e22c5",
>             "name": "One"
>         }]
>     }],
>     "options": [{
>         "code": "b64365ac185",
>         "id": "b64365ac185",
>         "name": "One"
>     }, {
>         "code": "b65ad0e22c5",
>         "id": "b65ad0e22c5",
>         "name": "One"
>     }]
> }
>
> Api Call: /api/metadata
>
> After the api call, the Hour option set is empty while the Minute option
> set has "One".
> Is this a defect in DHIS or we are missing something in our payload ?
> --
> Regards,
> Mansi Singhal
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>