Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Excel Reports point limit
-
Looking into this right now. Seems to be working fine for me but there's a little more to check out.
I'm noticing the new report isn't always added properly to the table of reports. It looks like the sort order isn't always obeyed. So, I would try swapping the sort order back and forth to ensure you're looking at the report you just triggered.
I am also wondering if you use the statistics tool on the data point details page if you get the delta you are expecting for the time period?
Edit: Also I wonder the versions of Core and Excel Reports you are using, but I am assuming you are on the latest of both.
-
I don't have delta listed under statistics.
And I have the reports emailing to me, so as long as its sends the new report, that's the one I am looking at.
Core version 2.8.8
excelReports 1.1.2 -
Alright, after some investigation I've resolved the following:
It's caused by a bug that was fixed in the 3.x series but no fix was released in 2.8 yet. I will try to get that prioritized. It'll probably get released either on Monday or Wednesday next week. This is in reference to the delta being zero. I haven't looked too deeply into the timestamps prev/past yet, I shall do that next. So, another resolution would be upgrading to Mango 3.
The good news is that you could work around it if need be. Since you're using a rollup period that's the same as your report period, you can change the rollup to none, and then change your named range to
myNamedRange.deltaand the point assigned tomyNamedRangewill have its delta for the whole report recorded in the .delta cell.Thanks for bringing this to our attention!
-
Thanks for finding that. I will wait for the update. Currently this is just in the testing phase and hasn't been implemented so I'll leave my named ranges as is. Thank you!
-
Hi,
Checking back in. I haven't seen the excel reports update yet. Any new ETA? Hoping to use the report in production soon. -
Hi Nathan,
Sorry for the delay. It will get released at some point tomorrow. Some good news is Craig found a bug in the purge of Excel Reports, so that fix will be in there too.
-
This has been released.
-
I'm not sure if the update solved my problem or created a new one. I have the report set to past 30 days with a 30 day rollup. The email body lists the correct date, but the time stamps in the excel file are incorrect.
-
I also get a system exception when going into system settings that looks related.
org.apache.jasper.JasperException: javax.servlet.ServletException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.ServletException: File "/modules/excelReports/web/settings.jspf" not found
-
Hi Nathan,
Oh my. You can resolve the issue on the system settings by renaming Mango/web/modules/excelReports/web/modules/excelReports/web/settings.txt to settings.jspf
I will put a version in the store that doesn't have this issue.
Edit: fixed in store
-
So I still have a problem that when the report runs, it isn't including the correct date range. I have it scheduled to run on the first of the month and the time period is 30 days with 30 day delta rollup. The email I received this morning showed the time as Time - 2017/07/03 00:00:00 EDT to 2017/08/01 00:00:00 EDT. But the excel file has timestamps of 6/23/17 12:00AM to 7/22/17 12:00AM. Any ideas on how to fix that?
-
Hi solarnathan,
I have been looking into it and I think there may be a problem with the rollup using days. Can you try a rollup of 720 hours instead of 30 days? We're working on it.
-
I changed the rollup to 720 hours, saved it, and then ran it. It locked up the mango for couple a minutes and didn't email the report. I went to the finished reports paged and clicked the download button. I get an error the file is not found. So I changed the time period to 720 hours. Now I get a report emailed with the correct time stamps, but incorrect data. One of the data fields is a timer that counts in second and it is only showing 57,600 seconds or 16 hours far away from the 720 hours it should be. I guess my next try will be to delete this report and try making one using myNamedRange.delta for all the fields.
-
Have you set your user's timezone and the timezone of the device?
