fix: data element category option combos as valid mapping candidates

[xurxodev]

📌 References

• Issue: Closes #?

📝 Implementation

• Restore the "dataElements" case in GenericMappingUseCase.getCategoryOptionCombos(), which was removed in [Fix] data elements warnings in mapping #907 (commit a4aebc5). That PR intended to stop generating a spurious inner category-option-combo mapping when a data element is the origin of an aggregated mapping (to avoid false conflict warnings on auto-map). As a side effect it also removed the ability to resolve category option combos when a data element is the destination of a mapping.
• This broke mapping a program indicator (or indicator) to a data element that has a real category combination (e.g. Gender: Male/Female): the "Category Option Combos" related-metadata mapping dialog only offered "default" instead of the destination data element's actual category option combos.
• Added a unit test (GetValidMappingIdUseCase.spec.ts) covering that getValidMappingIds returns the destination data element's category option combos as valid candidates.
• Verified manually that the original bug from [Fix] data elements warnings in mapping #907/[User feedback] Auto-map lists warnings even if there're no problems #1212 ("Auto-map lists warnings even if there're no problem") does not reappear: a later fix (falling back to the destination's real default COC instead of EXCLUDED_KEY in autoMapCollection) already prevents the false-conflict warning independently of this case.

📹 Screenshots/Screen capture

🔥 Is there anything the reviewer should know to test it?

• Map a program indicator to a data element that has a non-default category combination (e.g. Gender) in the destination instance.
• Open "Related metadata mapping" > "Category Option Combos" for that row.
• The picker should now list the destination data element's real category option combos (e.g. Male/Female), not just "default".

📑 Others

• Any change in the GUI library? If so, what branch/PR? No

• Any change in the D2 Api? If so, what branch/PR? No

[bundlemon]

BundleMon

No change in files bundle size

Groups updated (1)

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

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[anagperal]

thanks @xurxodev ! This fix works, but while testing this change I mapped a program indicator to a data element with a non-default category combination (Gender) in the destination. I completed both wizard steps — I mapped the origin default to the corresponding destination category option combo in Category Option Combos and in Attribute Option Combos — but the row still shows the "Mapping has errors" warning.

Why it happens
The Mapping has errors badge fires on conflicts || childrenConflicts (MappingTable.tsx:633), and conflicts is set as candidate.mappedId === EXCLUDED_KEY in autoMapCollection (GenericMappingUseCase.ts:280). The origin's default category option has no counterpart in a data element with a real category combo (Gender → Male/Female), so it falls back to EXCLUDED_KEY ("DISABLED") → conflicts: true in childrenConflicts

Suggested fix (same rationale as 9e2072c2): pass a destination-default fallback to the categoryOptions collection so the origin default option maps to the destination default instead of EXCLUDED_KEY

[xurxodev]

Hi @anagperal, I tried to reproduce the same issue you found but wasn't able to.

Could you confirm the exact steps you followed? Specifically:

• Local instance URL:
• Destination instance URL:
• Mapping between PI UID and DE UID in destination: (which program indicator and which destination data element did you map)
• Mapping between default and COC in destination: (in the Category Option Combos / Attribute Option Combos wizard step, what did you map the origin's "default" row to)
• Any additional steps or order of actions until you reproduce the warning

[anagperal]

@xurxodev

Hi @anagperal, I tried to reproduce the same issue you found but wasn't able to.

Could you confirm the exact steps you followed? Specifically:

• Local instance URL: https://play.im.dhis2.org/stable-2-42-5-1
• Destination instance URL: https://play.im.dhis2.org/stable-2-41-9
• Mapping between PI UID and DE UID in destination: (which program indicator and which destination data element did you map)
  PI in origin: XCMi7Wvnplm (BMI female)
  DE in destination: pnUtFI0hna9 (test Fem)

test-FEM-dataelement-and-dataset.json

• Mapping between default and COC in destination: (in the Category Option Combos / Attribute Option Combos wizard step, what did you map the origin's "default" row to)
  COC: HllvX50cXC0 (default) --> qk6n4eMAdtK (Female)
  Attribute Option Combo: HllvX50cXC0 (default) --> qk6n4eMAdtK (Female)

• Any additional steps or order of actions until you reproduce the warning

Video mapping PI BMI male to a clone of DE test Fem (test Male HQMG7okGWam )

Screencast.from.2026-07-07.17-08-13.webm

[anagperal]

DHIS2 Issue found while testing this PR : https://dhis2.atlassian.net/browse/DHIS2-21777

[xurxodev]

@anagperal ready

[anagperal]

@xurxodev thanks!! all ok