Error during metadata import (OU_LEVEL_DISTRICT>

[Don_Vieira (Immanuel Antonius - Vieira)]

Good day team

Importing metadata to a 2.37 instances. I’m getting this error below;

|vclhob0deoe|Predictor||Invalid reference [<OU_LEVEL_DISTRICT_UID>] (OrganisationUnitLevel) on object IDS - Acute Flacid Paralysis outbreak [vclhob0deoe] (Predictor) for association o**rganisationUnitLevels**.

It could have been easier if error was OU_UID, where once could go to an OrgUnit and copy the uid from Show details, but in this case its says OU_Level_District. Where does one get the UID for the level? When you go to OU_Level, you only get the offline levels 1,2,3…

Yes, I also tried using the UID of a district but didnt work.

Kindly assist

[Don_Vieira (Immanuel Antonius - Vieira)]

tracker @Gassim @YuryR Are you perhaps able to assist?

[YuryR (Yury Rogachev)]

Hi @Don_Vieira !

<OU_LEVEL_DISTRICT_UID> is a placeholder we leave for implementers to adjust based on the instance where they are going to use the package.

In your case, if you have districts configured in your system, check for the uid of the corresponding level:

../api/organisationUnitLevels

You will then replace <OU_LEVEL_DISTRICT_UID> with the uid of the corresponding level and import the package into your instance.

If you are aggregating your data on a different level, assign the uid accordingly.

In case you have levels labeled as 1,2,3,4 or have not given them a name, you may do so in the Maintenance app.

Remember to respect the syntax, when you replace the placeholder with the uid.

{
id: "<OU_LEVEL_DISTRICT_UID>"
}

will be replaced by i.e.

{
id: "OY67G4WhjQb"
}

Hope this helps!

[Don_Vieira (Immanuel Antonius - Vieira)]

@YuryR

../api/organisationUnitLevels

Thanks @YuryR, You just made my weekend!

Worked perfectly with the api option.

[munisha1 (Joseph Ayele)]

Dear Immanuel

Hope this message finds you well

Will you please, help me to resolve it, I encountered a problem while importing OU data. The data contained more than 10,000 entries in Excel, which I converted to CSV. However, the import summary showed zero records created, deleted, or updated. How can I resolve this issue? What step might I have missed, and what do you recommend? Please note that all prerequisites were implemented as suggested in the DHIS2 documentation.

Best!

Yosef