- jeansilva25841512Asked on July 15, 2014 at 07:57 PM
Tenho recebido reclamações que o relatório visual de um dos meus formulários, não está funcionando novamente.
fiz testes por algumas vezes durante o dia de hoje, e continua com o problema.
- JotForm SupportsteveAnswered on July 15, 2014 at 09:46 PM
We're sorry to hear about the inconvenience. I checked the link above, and I do not find a form in your account with that ID. It looks like someone deleted it, in which case the report will be no longer accessible.
I tried to reproduce this issue in my own account, and I'm also not able to view a report that I just created. I get a blank page as well. It's possible something changed in the system recently since we're improving the reports right now.
I'm going to have our developers take a look, and we'll update this thread when it's resolved.
Thank you for your patience.
- JotForm SupportpaulsimpsonAnswered on July 16, 2014 at 10:40 PM
This bug has now been fixed thank you for reporting it, and we are very sorry for any inconvenience it may have caused you.
- jeansilva25841512Answered on July 17, 2014 at 03:32 PM
realmente, voltou a funcionar até agora a pouco.
Mas parou novamente, e veja, quando abro para editar, mostra no rodapé o seguinte erro:
Fatal error: Cannot use object of type stdClass as array in /www/v3/builds/fba8cae66763540ef040ef8433b070ec7c0f9bd5/lib/classes/Reports/Data.php on line 294
Obrigado pela paciência em resolver essas situações.
Aguardo nova intervenção
- JotForm SupportBDAVIDAnswered on July 17, 2014 at 06:49 PM
Thanks for updating us in this matter, I can see only these two reports are showing the message, when trying to update:
Can you please try to create new reports and use Visual Report Filters?
- jeansilva25841512Answered on July 19, 2014 at 08:43 AM
Sim, somente estavam mostrando a mensagem, pois os demais ainda não apliquei filtros.
Verifico que, o erro ocorre ao aplicar filtro.
criei novos relatórios, (RELATORIO filtro: "Date Range" e RELATORIO 2, filtro: "Current Week") que funcionavam normalmente até eu aplicar um filtro a eles também:
LINK RELATÓRIO: http://www.jotform.com/report/41993895516067
LINK ATUALIZAR RELATÓRIO: http://www.jotform.com/page.php?p=reports&formID=40777720587970&reportID=41993895516067
MENSAGEM DE ERRO: Fatal error: Cannot use object of type stdClass as array in /www/v3/builds/e1864c1d4536debdad6b88698c1d0933a318e178/lib/classes/Reports/Data.php on line 294
O relatorio 2, ocorreu o mesmo.
Eu tambem não sou capaz de deletar os relatórios com o erro, ao tentar apagar, abre a tela para atualizar, com o erro mostrado acima.
- JotForm SupportjonathanAnswered on July 19, 2014 at 10:50 AM
I was able to see the error message you mentioned on the form report when I checked this report https://www.jotform.com/report/41993895516067 on your account.
when you Edit the Report it has an error message at the bottom of the Report Editor
The report http://www.jotform.com/report/41993895516067 is empty because there was actually no content on the report.
But let me do further test to try and find out the caused of the error in the report when editing in the report editor.
I will get back to you quickly with update on this.
- JotForm SupportjonathanAnswered on July 19, 2014 at 11:01 AM
Are you also able to add a new Visual Report on this form http://www.jotformpro.com/form/40777720587970 ?
I tried it on your account and I was able to create a new report
Can you try and saved the report. And then edit the report. Check if the error during edition will happen again on the new report.
We will wait for your updates.
- jeansilva25841512Answered on July 19, 2014 at 12:05 PM
Adicionei um novo relatório
NOME: visual report, jul 19
Eu era capaz de editar e salvar esse relatório normalmente, até quando incluí um filtro.
Após o filtro ele travou mostrando o mesmo erro.
Ou seja, os filtros estão causando erros em meus relatórios.
Em qualquer um que eu coloque um filtro, ele para de funcionar e eu não posso mais nem apagar esse relatório.
- JotForm SupportpaulsimpsonAnswered on July 19, 2014 at 07:13 PM
Thank you for reporting this. The error has now been fixed.