Dear Jason,
Please find the attached error.
On 3/25/17, Jason Pickering wrote:
> Hi Gerald,
> Check the server logs when you make the API call below. There seems to be
> an error here.
>
> https://sl.dhis2.org/hmis/api/dimensions/dataSet/UQGPrAQtDIV.json [HTTP/1.1
> 409 Conflict 435ms]
>
> Regar
Hi Gerald,
Check the server logs when you make the API call below. There seems to be
an error here.
https://sl.dhis2.org/hmis/api/dimensions/dataSet/UQGPrAQtDIV.json [HTTP/1.1
409 Conflict 435ms]
Regards,
Jason
On Sat, Mar 25, 2017, 05:01 gerald thomas wrote:
> Dear Jason,
> The only error fo
Dear Jason,
The only error found during the data set report process:
https://sl.dhis2.org/hmis/api/dataStatistics [HTTP/1.1 201 Created 184ms]
XML Parsing Error: no root element found
Location:
https://sl.dhis2.org/hmis/api/dataStatistics?eventType=DATA_SET_REPORT_VIEW&favorite=UQGPrAQtDIV
On
Ok. Please post it.
This error likely results from invalid HTML in your data set report form.
On Fri, Mar 24, 2017, 18:10 gerald thomas wrote:
> Dear Jason,
> I am receiving a parse error when I execute the report
>
> On Mar 24, 2017 22:05, "Jason Pickering"
> wrote:
>
> Are there any errors i
Dear Jason,
I am receiving a parse error when I execute the report
On Mar 24, 2017 22:05, "Jason Pickering"
wrote:
> Are there any errors in the browser console or the server when you
> execute the report?
>
> On Fri, Mar 24, 2017, 18:02 gerald thomas wrote:
>
>> Dear Jason,
>> It is a custom
Are there any errors in the browser console or the server when you execute
the report?
On Fri, Mar 24, 2017, 18:02 gerald thomas wrote:
> Dear Jason,
> It is a custom form but there is no JavaScript on it.
>
>
> On Mar 24, 2017 20:17, "Jason Pickering"
> wrote:
>
> Custom forms MAY work in dat
Dear Jason,
It is a custom form but there is no JavaScript on it.
On Mar 24, 2017 20:17, "Jason Pickering"
wrote:
> Custom forms MAY work in dataset reports, but it depends. Are you getting
> any JavaScript errors in the dataset reports? Any server errors?
> Are you using any custom JavaScript
Custom forms MAY work in dataset reports, but it depends. Are you getting
any JavaScript errors in the dataset reports? Any server errors?
Are you using any custom JavaScript in your forms?
On Fri, Mar 24, 2017 at 9:56 AM, Dapo Adejumo wrote:
> Hi Gerald,
> Unfortunately custom forms are not pro
Hi Gerald,
Unfortunately custom forms are not properly handled in dataset reports. A work
around will be to “print" the dataset report output to pdf using Chrome.
….
Dapo Adejumo
> On 24 Mar 2017, at 14:46, Mohamed Bangura wrote:
>
> Dear Gerald,
> Use mozilla firefox to extract th
Dapo,
Thanks for the information. Just wish there will be another way out soon.
On 3/24/17, Dapo Adejumo wrote:
> Hi Gerald,
> Unfortunately custom forms are not properly handled in dataset reports. A
> work around will be to “print" the dataset report output to pdf using
> Chrome.
> ….
Dear Gerald,
Use mozilla firefox to extract the data.
Do Ctrl A,Ctrl C
Open your blank excel and do ctrl V.
Hope this helps.
On 3/24/17, gerald thomas wrote:
> Dear all,
> Please i need your your help it is urgent.
>
> On 3/23/17, gerald thomas wrote:
>> Dear All,
>> I am having problems download
Yes it is a customer form.
On Mar 24, 2017 13:25, "Dapo Adejumo" wrote:
> Hi Gerald,
> Does this dataset use a custom form?
> ….
>
>
>
> *Dapo Adejumo*
>
> On 24 Mar 2017, at 13:57, gerald thomas wrote:
>
> Dear all,
> Please i need your your help it is urgent.
>
> On 3/23/17, gerald th
Hi Gerald,
Does this dataset use a custom form?
….
Dapo Adejumo
> On 24 Mar 2017, at 13:57, gerald thomas wrote:
>
> Dear all,
> Please i need your your help it is urgent.
>
> On 3/23/17, gerald thomas wrote:
>> Dear All,
>> I am having problems downloading Data Set report to excel
Dear all,
Please i need your your help it is urgent.
On 3/23/17, gerald thomas wrote:
> Dear All,
> I am having problems downloading Data Set report to excel or pdf. I am
> using version 2.25. It is working on demo but not on my instance.
> Please can someone help me with a fix.
>
> --
> Regards,
Hi Calle,
The issue was the umlaut that remained in RIPDA in the word naive and it
seemed that 1st and 2nd was somehow superscripted on other elements.
Once we corrected those the dataset report downloaded fine in excel and pdf.
Elmarie
On 28 Jan 2017 03:36, "Calle Hedberg" wrote:
> Elmarie,
Elmarie,
We have cleaned up many of the special characters in the data element and
indicator table fields, but a number remains (in particular full stops and
commas). There might be a few others - it's a lot to go through and a lot
of problems to clean up.
Exactly which special character caused t
Dear Elmarie,
I had done Data Integrity Checks but i don't know which option is
responsible for dataelements names with special characters. Besides we
had been doing data cleanup and we fixed most of those issues.
On 1/27/17, Elmarie Claasen wrote:
> Gerald,
>
> We had the same problem so e toim
Gerald,
We had the same problem so e toime back. Check that you dont have any
special characters in dataelement names.
Elmarie
On 27 Jan 2017 14:29, "gerald thomas" wrote:
> Dear All,
> We had successfully upgraded to version 2.25 but i noticed that we
> can't download to excel or PDF our data
18 matches
Mail list logo
