Closed rfromthecastle closed 1 year ago
Looks like the root cause here is the same corrupt data in the DHIS2 database, first discovered here: https://github.com/terraframe/geoprism-registry/issues/898#issuecomment-1507467413
If this was working in the past, it could be because the updated DHIS2 software is doing better validation of the translations (but hasn't patched out the existing corrupt data).
The following request: https://dhis2.asia/laohmis/api/metadata.json?organisationUnits=true&filter=id:eq:HTCt5PAPTQN
Reveals that there is an existing "description" translation without any locale:
{
"property": "DESCRIPTION",
"value": "ສຮສກ (ສາງໂຮງໝໍສູນກາງ)"
},
When our system attempts to submit changes to unrelated data, the DHIS2 notices the existing corrupt data and throws an error.
I will do the following:
Having difficulty replicating the bug on Staging and re-testing, so will only be able to test and confirm the fix is working once deployed to the Laos instance.
Working on the Laos instance. Thanks for fixing!
List the CGR information
Describe the bug (clear and concise) The error message details are empty when an external system synchronization fails.
To Reproduce
Expected behavior (clear and concise) Details of the error are provided.
Screenshots
Desktop (please complete the following information):
Additional context (if any)