[Dhis2-devs] Error while creating an event report with many options in DHIS 2.26 and DHIS 2.27

Support - Assistance technique
1

Hi,

In DHIS 2.26 and DHIS 2.27, we encountered the following error in the POST call while creating an event report with a data element that has many options in the filter.

{“httpStatus”:“Internal Server Error”,“httpStatusCode”:500,“status”:“ERROR”,“message”:“ERROR: value too long for type character varying(255)”}

We were only able to add 21 options to the filter and save the report in our case. Adding more than 21 options displayed the above error. We are suspecting that this is caused by the ‘filter’ parameter, when it crosses the 255 characters threshold (see below).

rows

:[{dimension: “aee50bae73b”, items: ,…}]

0:{dimension: “aee50bae73b”, items: ,…}

dimension:“aee50bae73b”

filter:“IN:ae5824ee166;af88bde6615;a4e5da8828d;a342292ba70;a8b2ff2daf1;ab81f48f895;a0c83d60c8d;a440a1a53ec;af99d73c133;af80977531e;af430c7dd91;aecabb2c41d;a31fd3b9ffd;a8be7cafaeb;ad4969e1f34;a76e39e60dc;ab99d76f26c;aecdba37c76;af294a21e9f;a4b890e3441;a5c5340a7ee;a0d75d2c0b6”

items:

name:“Primary Diagnosis at ICU Discharge - Discharge - Intensive Care Ward”

We also tried to replicate this in DHIS play. Though we were not able to create the event report in DHIS play as well, the error reported was different (See attached screenshot). Could you please confirm if this is a bug?

image

···

Thanks
Preeti Ajgaonkar

2

Looping in Marta.

···

On Wed, Dec 20, 2017 at 3:27 PM, Preeti Ajgaonkar apreeti@thoughtworks.com wrote:

Hi,

In DHIS 2.26 and DHIS 2.27, we encountered the following error in the POST call while creating an event report with a data element that has many options in the filter.

{“httpStatus”:“Internal Server Error”,“httpStatusCode”:500,“status”:“ERROR”,“message”:“ERROR: value too long for type character varying(255)”}

We were only able to add 21 options to the filter and save the report in our case. Adding more than 21 options displayed the above error. We are suspecting that this is caused by the ‘filter’ parameter, when it crosses the 255 characters threshold (see below).

rows

:[{dimension: “aee50bae73b”, items: ,…}]

0:{dimension: “aee50bae73b”, items: ,…}

dimension:“aee50bae73b”

filter:“IN:ae5824ee166;af88bde6615;a4e5da8828d;a342292ba70;a8b2ff2daf1;ab81f48f895;a0c83d60c8d;a440a1a53ec;af99d73c133;af80977531e;af430c7dd91;aecabb2c41d;a31fd3b9ffd;a8be7cafaeb;ad4969e1f34;a76e39e60dc;ab99d76f26c;aecdba37c76;af294a21e9f;a4b890e3441;a5c5340a7ee;a0d75d2c0b6”

items:

name:“Primary Diagnosis at ICU Discharge - Discharge - Intensive Care Ward”

–
Thanks
Preeti Ajgaonkar

We also tried to replicate this in DHIS play. Though we were not able to create the event report in DHIS play as well, the error reported was different (See attached screenshot). Could you please confirm if this is a bug?