We are working on migrating data from one instance to another, where the instances have different configurations for the data elements. In the data extracted from one instance, we have to change the following element values to correspond to those of the instance to which we are importing data:- dataElement, categoryOptionCombo and attributeOptionCombo. The first two i.e. dataElement and categoryOptionCombo we can get through the API, but the attributeOptionCombo value can’t be got through the API. We have two questions.
Where in a DHIS2 instance can we get the attributeOptionCombo value for a given dataset?
If we migrate data using this method, does this affect the Reporting Rate for that particular DataSet? If it does, how can we overcome this?
attributeOptionCombo is still just a categoryOptionCombo (with a different name), you will find these at the same endpoint at categoryOptionCombos.
Regarding pt 2, I’m not 100%… but reporting rate is linked to completenes on the data set, so I don’t think that would be affected
···
On Wed, Apr 6, 2016 at 6:46 PM, Mugeni Harold hmugeni@gmail.com wrote:
Hallo devs,
We are working on migrating data from one instance to another, where the instances have different configurations for the data elements. In the data extracted from one instance, we have to change the following element values to correspond to those of the instance to which we are importing data:- dataElement, categoryOptionCombo and attributeOptionCombo. The first two i.e. dataElement and categoryOptionCombo we can get through the API, but the attributeOptionCombo value can’t be got through the API. We have two questions.
Where in a DHIS2 instance can we get the attributeOptionCombo value for a given dataset?
If we migrate data using this method, does this affect the Reporting Rate for that particular DataSet? If it does, how can we overcome this?
Thank you for the reply, but we realized that after importing the data, when we checked the reporting rate for that month, it was saying that no data had been reported for that period, until we went into data entry and for that form and period, though we could see the data, we had to click on the “complete” button and it is at this point that the reporting rate was as expected. So my questions are:-
What does clicking on the “complete” button do internally?
How can we export the result of clicking on the “complete” button with the data itself?
Thank you,
Harold
···
From: Morten Olav Hansen [mailto:morten@dhis2.org] Sent: Thursday, April 07, 2016 5:17 AM To: Mugeni Harold Cc: dhis2-devs Subject: Re: [Dhis2-devs] Attribute Option Combo Value
Hi Mugeni
attributeOptionCombo is still just a categoryOptionCombo (with a different name), you will find these at the same endpoint at categoryOptionCombos.
Regarding pt 2, I’m not 100%… but reporting rate is linked to completenes on the data set, so I don’t think that would be affected
On Wed, Apr 6, 2016 at 6:46 PM, Mugeni Harold hmugeni@gmail.com wrote:
Hallo devs,
We are working on migrating data from one instance to another, where the instances have different configurations for the data elements. In the data extracted from one instance, we have to change the following element values to correspond to those of the instance to which we are importing data:- dataElement, categoryOptionCombo and attributeOptionCombo. The first two i.e. dataElement and categoryOptionCombo we can get through the API, but the attributeOptionCombo value can’t be got through the API. We have two questions.
Where in a DHIS2 instance can we get the attributeOptionCombo value for a given dataset?
If we migrate data using this method, does this affect the Reporting Rate for that particular DataSet? If it does, how can we overcome this?