I have an automatic process that create all the configuration of the DHIS by using the Web API and Pentaho data integration. However, I think that there is some changes in the API (since 2.16) that i do not understand well. Basically, in certain point of the process, we query “organisationUnitLevels” and the “level” property. Specifically, we query in json format: http://localhost:8080/dhis/api/organisationUnitLevels.json. However, in new API this property do not come in the response. Furthermore, if you export level metadata you can notice that this property still exist in the system. Is this correct, it will be reimplemented or theres is no way to query this property of levels by using the API?. I have some workaround in mind, however, I will wait for some feedback in order to implemement.
Thanks in advance for the response,
Regards,
Octavio.
PD: Following some examples obtained through quering Web API:
I have an automatic process that create all the configuration of the DHIS by using the Web API and Pentaho data integration. However, I think that there is some changes in the API (since 2.16) that i do not understand well. Basically, in certain point of the process, we query “organisationUnitLevels” and the “level” property. Specifically, we query in json format: http://localhost:8080/dhis/api/organisationUnitLevels.json. However, in new API this property do not come in the response. Furthermore, if you export level metadata you can notice that this property still exist in the system. Is this correct, it will be reimplemented or theres is no way to query this property of levels by using the API?. I have some workaround in mind, however, I will wait for some feedback in order to implemement.
Thanks in advance for the response,
Regards,
Octavio.
PD: Following some examples obtained through quering Web API:
Hi,
you can specify which fields you need, including the levels: /api/organisationUnitLevels.json?fields=name,id,level etc…
Olav
I have an automatic process that create all the configuration of the DHIS by using the Web API and Pentaho data integration. However, I think that there is some changes in the API (since 2.16) that i do not understand well. Basically, in certain point of the process, we query “organisationUnitLevels” and the “level” property. Specifically, we query in json format: http://localhost:8080/dhis/api/organisationUnitLevels.json. However, in new API this property do not come in the response. Furthermore, if you export level metadata you can notice that this property still exist in the system. Is this correct, it will be reimplemented or theres is no way to query this property of levels by using the API?. I have some workaround in mind, however, I will wait for some feedback in order to implemement.
Thanks in advance for the response,
Regards,
Octavio.
PD: Following some examples obtained through quering Web API:
I have an automatic process that create all the configuration of the DHIS by using the Web API and Pentaho data integration. However, I think that there is some changes in the API (since 2.16) that i do not understand well. Basically, in certain point of the process, we query “organisationUnitLevels” and the “level” property. Specifically, we query in json format: http://localhost:8080/dhis/api/organisationUnitLevels.json. However, in new API this property do not come in the response. Furthermore, if you export level metadata you can notice that this property still exist in the system. Is this correct, it will be reimplemented or theres is no way to query this property of levels by using the API?. I have some workaround in mind, however, I will wait for some feedback in order to implemement.
Thanks in advance for the response,
Regards,
Octavio.
PD: Following some examples obtained through quering Web API: