Unable to view previous Program indicators of expression Event Count in 2.33

We were previously on 2.28 and now upgrading to 2.33

Program indicators of of expression Event Count show blank in Pivot tables in 2.33

Any idea how can we fix this

1 Like

Hi @Dipali_Sahu.

Thank you for reporting this issue.

Is it the same issue as mentioned here?
https://jira.dhis2.org/browse/DHIS2-8580

Do you also get the java.lang.Long cannot be cast to java.lang.Double error if you try to visualize the program indicators in Data Visualizer?

Best regards,
Karoline

Hi @Dipali_Sahu ,

We had the same issue and we realized that all those indicators had in common that they contained program indicators with decimals sets to 0.

Instead we set them as from the Maintenance app

If you have a lot of cases like that a quicker option is to extract the metadata content of those programindicators with the following query

/api/metadata?programIndicators:filter=decimals:eq:0

Remove the parameter from the payload and reimport them again (with merge mode as REPLACE)

Hope this also solve your issue.

1 Like

Hi Karoline
Thank you for the response, Yes looks similar issue however,

I don’t seem to get any error, it just shows blank page, both in Data visualizer and Pivot tables. (see screenshot).

Hi Eric, thank you for the response.

I am getting this error irrespective of the “Decimal” field value, across all the reports( and we have too many program indicators since we collect lot of individual data). In many places the decimal field is blank in our case. Also, most of our indicators are Event counts with different filters and expressions.

I will anyhow investigate further and see if I can find any commonalities

1 Like

good copy, thank you! Yes, please if you find more information keep the community posted :slight_smile:

Hi Karoline

Any update on this one?

Thank you

Hi @Dipali_Sahu,

Sorry for the delayed response.

The JIRA issue I mentioned, https://jira.dhis2.org/browse/DHIS2-8580, was fixed in the 2.33.3 patch which was released in April. Have you tested with that patch to see if your issue still persists?

Best regards,
Karoline