← Back to team overview

dhis2-devs team mailing list archive

Defect in metadata import for optionSets?

 

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

Follow ups