[fix]: Compulsory DE operands import error

[deeonwuli]

📌 References

• Issue: Closes https://app.clickup.com/t/869cemv66

📝 Implementation

Problem: When dataSets are exported, compulsory data element operands may lack a categoryOptionCombo.id, causing import failures.
Solution: This fix ensures all data element operands in the dataset payload have valid coc id, defaulting to the "default" coc id if not present

📹 Screenshots/Screen capture

📑 Others

#869cemv66

[bundlemon]

BundleMon

No change in files bundle size

Groups updated (1)

Status	Path	Size	Limits
✅	Build Folder ./**/*	2.75MB (+44B 0%)	+20%

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[gqcorneby]

[code-only review] Thanks @deeonwuli! Just some minor comments and clarifications :)

[gqcorneby]

defaultCategoryOptionCombo will always be truthy at this point because a guard is in place after declaration. The ternary operation can be simplified into a spread directly

[gqcorneby]

Might be worth adding a test for when getCategoryOptionCombos returns a real combo, verifying that operands with a missing categoryOptionCombo.id get it replaced with the default one.

[gqcorneby]

[code-only review] Thanks @deeonwuli!!

[xurxodev]

Thanks @deeonwuli

I tried test following the steps in the task using the dataset that indicate the task in our WIDP instance but I can't because it's failing a sync using dataset NTD GNARF(NnhyjiUbcJN)

I did a direct url call and the compulsory data element operands is ok.

This PR asume this bug and patch the payload if categoryOptionCombo.id is empty but what is the reason for this situation in the sync?

because a direct api url is ok how you can see in the image and this url: https://dev.eyeseetea.com/who-dev-41/api/dataSets/NnhyjiUbcJN?fields=id,name,compulsoryDataElementOperands

In this moment I have the doubt if it's possible fix the problem without patch the payload but in the previous calls. I don't know if you reviewed this possibility, if it's possible the patch is not necessary and the fix should be done before.

Anyway I can't tests because the sync is failing, can you review it?

[deeonwuli]

Hi @xurxodev, thanks for the review. You were right that patching the payload was not fixing it at the source.

I found that the root cause was MetadataD2ApiRepository.getMetadata was calling /api/metadata with defaults=EXCLUDE. For datasets, this strips the default categoryOptionCombo.id from every object in compulsoryDataElementOperands.

Fix: Instead of correcting operands during payload construction, the fetch itself now preserves those nested default references:

About the testing blocker (NTD GNARF / 500 error): I raised the issue with Arnau in this ClickUp task. This error has not been further explored and has not come up in any of our other projects yet. So it looks unrelated to this PR.