Analytics fails in 2.41.9 when type of data Element with category combo

Development - Développement
1

Dear Community,
After upgrading from 2.40.2.2 to 2.41.9

Analytics fails when a Text/Long Text data element with a category combo contains a value with the letter E, for example: 224E10000913 or 46E-1309013 (Aggregate/Dataset)
This is a serial number, but Analytics appears to interpret it as scientific notation and aborts with:
Processing aborted: skipped stage, failing item caused abort.

log:> ERROR: “46E-1309013” is out of range for type double precision

The issue does not occur in 2.40.2.2 and replacing E with another character allows Analytics to complete successfully.
I was also able to reproduce the same issue on Login app | DHIS2.
Is this expected behavior or bug.?

2

Bug for sure. What was the procedure to reproduce it on the play server?

3
  1. Create a dataset assign a LONG_TEXT data element with a category combination (Serial No and Model)
  2. Assign the dataset to an organisation unit. Daily
  3. Enter a value such as 224E10000913 for the Serial No or Model category option. (Entry for Any 3 to 4 Random Periods)
  4. Run Analytics.

Actual Result:
Analytics generation Failed with Error at Data Administration Section

4

Hi @arslan_mughal

These steps demonstrate that the issue is triggered specifically by text values containing the letter E, which appear to be incorrectly parsed as scientific notation during analytics processing.

Since the behavior does not occur in version 2.40.2.2 and is reproducible on another DHIS2 instance, it strongly suggests a regression bug rather than expected behavior.

5

I have tried to reproduce faithfully the issue as you describe both on the latest development version of DHIS2 and on Login app | DHIS2. I used the attached dataset.

I entered some data like this

image
image1507×454 48.2 KB

Triggered analytics, and the process completed successfully.

metadata.json (14.6 KB)

Perhaps I missed something in the procedure to replicate the issue?

Best regards,
Jason

6

image
image1861×788 75.3 KB

on play Login app | DHIS2

error state.json (229.6 KB)

7

So, I see now that you triggered the analytics on the play server (which should be restricted actually) using the scheduler app. I had triggered it via the data administration app. It worked via the data administration app but not via the scheduler.

The difference I think was this:

image
image362×132 6.27 KB

This is definitely a bug. We will get it fixed, but in the meantime, disable outliers (which you should probably due anyway) when generating analytics.

Best regards,
Jason