In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 17, 2016 at 7:24 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Thank you Morten.
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 17, 2016 at 7:10 PM, Morten Olav Hansen morten@dhis2.org wrote:
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
On Wed, Aug 24, 2016 at 12:33 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Hi Morten,
Just wondering whether this has been fixed.
Thank you
On Wed, Aug 17, 2016 at 7:24 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Thank you Morten.
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 17, 2016 at 7:10 PM, Morten Olav Hansen morten@dhis2.org wrote:
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
On Wed, Aug 24, 2016 at 12:33 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Hi Morten,
Just wondering whether this has been fixed.
Thank you
On Wed, Aug 17, 2016 at 7:24 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Thank you Morten.
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 17, 2016 at 7:10 PM, Morten Olav Hansen morten@dhis2.org wrote:
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Thu, Aug 25, 2016 at 12:50 PM, Morten Olav Hansen morten@dhis2.org wrote:
Give our servers about 1 hour, and you can download the fix for 2.23, 2.24 and trunk
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 24, 2016 at 12:33 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Hi Morten,
Just wondering whether this has been fixed.
Thank you
On Wed, Aug 17, 2016 at 7:24 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Thank you Morten.
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 17, 2016 at 7:10 PM, Morten Olav Hansen morten@dhis2.org wrote:
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
We found a problem in the SQL Views as well. SQLView/{id}/data endpoint is not working in v2.24 (23583,2016-08-25 07:50) and we can’t even define new SQL views from the Data Administration app.
On Thu, Aug 25, 2016 at 12:50 PM, Morten Olav Hansen morten@dhis2.org wrote:
Give our servers about 1 hour, and you can download the fix for 2.23, 2.24 and trunk
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 24, 2016 at 12:33 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Hi Morten,
Just wondering whether this has been fixed.
Thank you
On Wed, Aug 17, 2016 at 7:24 PM, Pamod Amarakoon pamodm@gmail.com wrote:
Thank you Morten.
–
Regards,
Pamod Amarakoon
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
On Wed, Aug 17, 2016 at 7:10 PM, Morten Olav Hansen morten@dhis2.org wrote:
Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.
In our setup, we have 5 orgUnitLevels and above query works fine for superuser who has just one orgUnit assigned which is of level 1.
There are other users who has multiple level 4 and 5 orgUnits assigned. Above API call fails for those users giving a 500 error code. Basically this doesn’t work for any user who has multiple orgUnits.
The cause for the issue seems to be a SQL syntax error.
