we have defined dataelements with a non-default category. The values of these dataelements come from the aggregation of individual data values. The “manual aggregation” process works fine, and the values are correctly stored in the database.
The problem is that these values do not appear in the “Services -> Data Entry” module. But, however, if the values are introduced manually in the Data Entry module instead of using the aggregation process, the values do appear.
I have checked the datavalue table in the database and there is a difference between them:
When the value is stored using the aggregation process, the “attributeoptioncomboid” field takes the same value as the “categoryoptioncomboid” field.
When the value is introduced manually in the Data Entry module, the “attributeoptioncomboid” field takes the default value (15).
Finally, if the dataelement category is default, the value correctly appears in the Data Entry module, however it is introduced. The problem only occurs when the dataelement category is not default.
We are using the version 2.14 revision 13807.