Import/Export DataElementOperand

Bug #1250403 reported by Paulo Grácio on 2013-11-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Morten Olav Hansen

Bug Description

Hi Morten,

We are facing a problem during export/import, once dataelementoperand is empty after import.

We found this:


// special class which is created on demand in association with other objects
exportClasses.remove( DataElementOperand.class );
importClasses.remove( DataElementOperand.class );

Is there a way to regenerate this table?

Thanks for your help.

Paulo Grácio (pgracio) wrote :


I don't remember the exact details, but compulsoryDataElementOperands/greyedFields was disabled because it caused issues with our importer, I think it was related to how they are stored (which is different from the rest of our types).

If it's important, we might be able to look at it before the 2.14 release.. can you create a bug report for it?


Changed in dhis2:
assignee: nobody → Morten Olav Hansen (mortenoh)
importance: Undecided → Medium
milestone: none → 2.13
Morten Olav Hansen (mortenoh) wrote :

Fixed in trunk and backported to 2.13. Please check and verify.

Changed in dhis2:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers