← Back to team overview

dhis2-devs team mailing list archive

Inconsistent behavior between dataValues and dataValueSets endpoints in regards to data set period expiry

 

Hi Devs,
When data is imported through the API through the dataValues end point, it
appears that if a data set which the data elements which are being reported
has an period which is locked (or expired) it is not possible to import the
data. You get a message like

{"httpStatus":"Conflict","httpStatusCode":409,"status":"ERROR","message":"Data
set is locked"}

When you import the same data through the dataValueSets endpoint, it works.

In this case, you get

{"responseType":"ImportSummary","status":"SUCCESS","description":"Import
process completed
successfully","importCount":{"imported":21,"updated":0,"ignored":0,"deleted":0},"dataSetComplete":"false"}

as an example.

This does not seem to be entirely consistent behavior. Is this being
considered to be implemented in a future release?

Regards,
Jason

Follow ups