After migrate to 2.12 version, the aggregation query builder doesn’t aggregate the values in the data element. We test with new data elements, simple queries but doesn’t work. Maybe the new version has other parameters to aggregate the values?.
Thank you very much.
···
–
Regards,
Ing. Marko David Garcia M.
**Área de Sistemas integrados de Información
Secretaría de Salud Departamental del Cauca
**
Hi, We have reviewed in detail and we found that the problem is presented with aggregation query that use the attribute of patient that we have created.
The postgres console print the next error.
ERROR: syntax error at or near ")" at character 617
STATEMENT: SELECT '0' as dataelementid, '0' as categoryoptioncomboid, ou.organisationunitid as sourceid, '0' as periodid,'DHIS-SYSTEM' as comment, '201308' as periodIsoDate,'dataelementname' as dataelementname, 'optioncomboid' as categoryoptioncomboname, ou.name as organisationunitname, count (psi.programinstanceid ) as value FROM programstageinstance as psi INNER JOIN organisationunit ou on ou.organisationunitid=psi.organisationunitid WHERE EXISTS ( SELECT * FROM patientattributevalue _pav WHERE _pav.patientid = pi.patientid and _pav.patientattributeid=280 AND p.organisationunitid in (0) AND _pav.value )='Especial' ) GROUP BY ou.organisationunitid, ou.name
the error is generated when we edit the aggregation query, but it is don't generated with aggregation query that use the attibutes of patient that it is by default. (Sex).
Thanks,
ING. Helder Yesid Castrillon.
Secretaría departamental de salud
Hi, We have reviewed in detail and we found that the problem is presented with aggregation query that use the attribute of patient that we have created.
The postgres console print the next error.
__ERROR: syntax error at or near “)” at character 617
STATEMENT: SELECT ‘0’ as dataelementid, ‘0’ as categoryoptioncomboid, ou.organisationunitid as sourceid, ‘0’ as periodid,‘DHIS-SYSTEM’ as comment, ‘201308’ as periodIsoDate,‘dataelementname’ as dataelementname, ‘optioncomboid’ as categoryoptioncomboname, ou.name as organisationunitname, count (psi.programinstanceid ) as value FROM programstageinstance as psi INNER JOIN organisationunit ou on ou.organisationunitid=psi.organisationunitid WHERE EXISTS ( SELECT * FROM patientattributevalue _pav WHERE _pav.patientid = pi.patientid and pav.patientattributeid=280 AND p.organisationunitid in (0) AND pav.value )=‘Especial’ ) GROUP BY ou.organisationunitid, ou.name
the error is generated when we edit the aggregation query, but it is don’t generated with aggregation query that use the attibutes of patient that it is by default. (Sex).
After migrate to 2.12 version, the aggregation query builder doesn’t aggregate the values in the data element. We test with new data elements, simple queries but doesn’t work. Maybe the new version has other parameters to aggregate the values?.
Thank you very much.
–
Regards,
Ing. Marko David Garcia M.
**Área de Sistemas integrados de Información
Secretaría de Salud Departamental del Cauca
**
Hi, We have reviewed in detail and we found that the problem is presented with aggregation query that use the attribute of patient that we have created.
The postgres console print the next error.
__ERROR: syntax error at or near “)” at character 617
STATEMENT: SELECT ‘0’ as dataelementid, ‘0’ as categoryoptioncomboid, ou.organisationunitid as sourceid, ‘0’ as periodid,‘DHIS-SYSTEM’ as comment, ‘201308’ as periodIsoDate,‘dataelementname’ as dataelementname, ‘optioncomboid’ as categoryoptioncomboname, ou.name as organisationunitname, count (psi.programinstanceid ) as value FROM programstageinstance as psi INNER JOIN organisationunit ou on ou.organisationunitid=psi.organisationunitid WHERE EXISTS ( SELECT * FROM patientattributevalue _pav WHERE _pav.patientid = pi.patientid and pav.patientattributeid=280 AND p.organisationunitid in (0) AND pav.value )=‘Especial’ ) GROUP BY ou.organisationunitid, ou.name
the error is generated when we edit the aggregation query, but it is don’t generated with aggregation query that use the attibutes of patient that it is by default. (Sex).
After migrate to 2.12 version, the aggregation query builder doesn’t aggregate the values in the data element. We test with new data elements, simple queries but doesn’t work. Maybe the new version has other parameters to aggregate the values?.
Thank you very much.
–
Regards,
Ing. Marko David Garcia M.
**Área de Sistemas integrados de Información
Secretaría de Salud Departamental del Cauca
**
It works with formula [CA:43567] = ‘Gender’. For formulas like this [CA:43567] = Gender (Gender didn’t put between apostroph ), formulas didn’t work. So if you have any formula similar to the second case, please put value to compare between apostroph (') . This bug will be fixed for 2.13 version as plan.
Hi, We have reviewed in detail and we found that the problem is presented with aggregation query that use the attribute of patient that we have created.
The postgres console print the next error.
__ERROR: syntax error at or near “)” at character 617
STATEMENT: SELECT ‘0’ as dataelementid, ‘0’ as categoryoptioncomboid, ou.organisationunitid as sourceid, ‘0’ as periodid,‘DHIS-SYSTEM’ as comment, ‘201308’ as periodIsoDate,‘dataelementname’ as dataelementname, ‘optioncomboid’ as categoryoptioncomboname, ou.name as organisationunitname, count (psi.programinstanceid ) as value FROM programstageinstance as psi INNER JOIN organisationunit ou on ou.organisationunitid=psi.organisationunitid WHERE EXISTS ( SELECT * FROM patientattributevalue _pav WHERE _pav.patientid = pi.patientid and pav.patientattributeid=280 AND p.organisationunitid in (0) AND pav.value )=‘Especial’ ) GROUP BY ou.organisationunitid, ou.name
the error is generated when we edit the aggregation query, but it is don’t generated with aggregation query that use the attibutes of patient that it is by default. (Sex).
After migrate to 2.12 version, the aggregation query builder doesn’t aggregate the values in the data element. We test with new data elements, simple queries but doesn’t work. Maybe the new version has other parameters to aggregate the values?.
Thank you very much.
–
Regards,
Ing. Marko David Garcia M.
**Área de Sistemas integrados de Información
Secretaría de Salud Departamental del Cauca
**
It is not our case, all the formulas has apostroph (') in the values. We have identified that the bug is when we do aggregation query using the patients attributes created by us.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
On Fri, Aug 30, 2013 at 3:49 AM, helder yesid castrillon cobo helder_947@hotmail.com wrote:
It is not our case, all the formulas has apostroph (') in the values. We have identified that the bug is when we do aggregation query using the patients attributes created by us.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
It works with formula [CA:43567] = ‘Gender’. For formulas like this [CA:43567] = Gender (Gender didn’t put between apostroph ), formulas didn’t work. So if you have any formula similar to the second case, please put value to compare between apostroph (') . This bug will be fixed for 2.13 version as plan.
Hi, We have reviewed in detail and we found that the problem is presented with aggregation query that use the attribute of patient that we have created.
The postgres console print the next error.
__ERROR: syntax error at or near “)” at character 617
STATEMENT: SELECT ‘0’ as dataelementid, ‘0’ as categoryoptioncomboid, ou.organisationunitid as sourceid, ‘0’ as periodid,‘DHIS-SYSTEM’ as comment, ‘201308’ as periodIsoDate,‘dataelementname’ as dataelementname, ‘optioncomboid’ as categoryoptioncomboname, ou.name as organisationunitname, count (psi.programinstanceid ) as value FROM programstageinstance as psi INNER JOIN organisationunit ou on ou.organisationunitid=psi.organisationunitid WHERE EXISTS ( SELECT * FROM patientattributevalue _pav WHERE _pav.patientid = pi.patientid and pav.patientattributeid=280 AND p.organisationunitid in (0) AND pav.value )=‘Especial’ ) GROUP BY ou.organisationunitid, ou.name
the error is generated when we edit the aggregation query, but it is don’t generated with aggregation query that use the attibutes of patient that it is by default. (Sex).
After migrate to 2.12 version, the aggregation query builder doesn’t aggregate the values in the data element. We test with new data elements, simple queries but doesn’t work. Maybe the new version has other parameters to aggregate the values?.
Thank you very much.
–
Regards,
Ing. Marko David Garcia M.
**Área de Sistemas integrados de Información
Secretaría de Salud Departamental del Cauca
**
Ok, I tested with revisions 11245 and 11290 but the error persist, today I downloaded Dhis the web site (http://www.dhis2.org/downloads\), however it is the same revision (11290).
How I download DHIS 2.12 with revision 11291?.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
Hi,
I downloaded DHIS 2.13-SNAPSHOT with revision 11846 from DHIS2 App Hub to test, but in this revision the error persist, also we tested in the demo of DHIS to discard errors in ours Data, obtaining the same error.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
This bug was fixed for only 1.12 version. For 2.13, we have a plan to improve it by using web-API. And I am working on it.
I tested this bug on demo server ( with revision 11292 in this morning), it works fine. Can you help me to test it again ?
Best regard,
···
On 30-08-2013, at 23:42, helder yesid castrillon cobo <helder_947@hotmail.com> wrote:
Hi,
I downloaded DHIS 2.13-SNAPSHOT with revision 11846 from DHIS2 App Hub to test, but in this revision the error persist, also we tested in the demo of DHIS to discard errors in ours Data, obtaining the same error.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
Hi,
I downloaded DHIS 2.13-SNAPSHOT with revision 11846 from http://apps.dhis2.org/ci/job/dhis-web-2.12/ to test, but in this revision the error persist, also we tested in the demo of DHIS to discard errors in ours Data, obtaining the same error.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
Ok, I tested with revisions 11245 and 11290 but the error persist, today I downloaded Dhis the web site (http://www.dhis2.org/downloads), however it is the same revision (11290)
How I download DHIS 2.12 with revision 11291?.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
On Fri, Aug 30, 2013 at 3:49 AM, helder yesid castrillon cobo helder_947@hotmail.com wrote:
It is not our case, all the formulas has apostroph (') in the values. We have identified that the bug is when we do aggregation query using the patients attributes created by us.
Mg. Helder Yesid Castrillon.
Sistemas de información
Secretaría departamental de salud del cauca.
It works with formula [CA:43567] = ‘Gender’. For formulas like this [CA:43567] = Gender (Gender didn’t put between apostroph ), formulas didn’t work. So if you have any formula similar to the second case, please put value to compare between apostroph (') . This bug will be fixed for 2.13 version as plan.
Hi, We have reviewed in detail and we found that the problem is presented with aggregation query that use the attribute of patient that we have created.
The postgres console print the next error.
__ERROR: syntax error at or near “)” at character 617
STATEMENT: SELECT ‘0’ as dataelementid, ‘0’ as categoryoptioncomboid, ou.organisationunitid as sourceid, ‘0’ as periodid,‘DHIS-SYSTEM’ as comment, ‘201308’ as periodIsoDate,‘dataelementname’ as dataelementname, ‘optioncomboid’ as categoryoptioncomboname, ou.name as organisationunitname, count (psi.programinstanceid ) as value FROM programstageinstance as psi INNER JOIN organisationunit ou on ou.organisationunitid=psi.organisationunitid WHERE EXISTS ( SELECT * FROM patientattributevalue _pav WHERE _pav.patientid = pi.patientid and pav.patientattributeid=280 AND p.organisationunitid in (0) AND pav.value )=‘Especial’ ) GROUP BY ou.organisationunitid, ou.name
the error is generated when we edit the aggregation query, but it is don’t generated with aggregation query that use the attibutes of patient that it is by default. (Sex).
After migrate to 2.12 version, the aggregation query builder doesn’t aggregate the values in the data element. We test with new data elements, simple queries but doesn’t work. Maybe the new version has other parameters to aggregate the values?.
Thank you very much.
–
Regards,
Ing. Marko David Garcia M.
**Área de Sistemas integrados de Información
Secretaría de Salud Departamental del Cauca
**