I would like to draw your attention to the translation part of any metadata API. Particularly somehow when user add the translation, some previous translations got duplicated. Would it be possible to fix it? So before to update or store NAME, SHORT_NAME,DESCRIPTION properties via API DHIS should check if there is translation for the selected language and property?
As there is no control I have faced following problems as shown in the picture above. It could be easily fixed, but instead of providing the UID of the element it shows its index, which is not clear and if there are 1000 elements to be imported, the user should count each manually.
When I tried, I got that files with duplicate translations were rejected, and that files containing new translations overwrote the existing ones (which is the expected behavior).
Thank you for your reply. The issues with translations not happening often and have no idea when and how it may happen. But the fact is if that happened you will be unnoticed until you start sync or import metadata.
I have tried to reproduce but couldn’t.
Therefore I believe would be great just to provide UID of the element which cause an error, instead of providing index or just general message.
Also recently found that if username exists for the other user with same username but different UID the import/export app will fail without providing any explanations
