I have a report that uses a table group. With 17 peer tables set to break on pages.
I’ll get timeout exceptions when I’m emailing from the designer or trying to save to file and the CPU will go above 70% and will take about a min to complete.
All data keys come from dataset tags. At first, they were named queries. So I made them into tags thinking that was the issue. Because this query can take almost 500ms to run. And there isn’t a whole lot I can do to improve it right now…
I am working on trying that right now. I’ll report back with details. If its any less resource intensive. I’m on 8.06 and going to update to 8.1 over thanksgiving. So I could name the sheets then! Which is bonus I don’t think I could get from the Reporting Module.
Traceback (most recent call last):
File "<input>", line 15, in <module>
AttributeError: 'com.inductiveautomation.ignition.designer.gui.tool' object has no attribute 'toExcel'
## Specify the paths
#paths = [
# "[default]D01/D01/Data/Database/Production/Produciton.Value",
# "[default]D02/D02/Data/Database/Production/Produciton.Value"
# ]
#
## Send the reads off
#results = system.tag.readBlocking(paths)
var = system.tag.read("[default]D02/D02/Data/Database/Production/Produciton.Value")
print var.value
spreadsheet = system.dataset.toExcel(True, [var.value])
filePath = "C:\\Ignition Reports"
system.file.writeFile(filePath, spreadsheet)
I don’t guess you can do this from script console.
What is a sequence of datasets? is it not a list? This script makes a corupted .xls
#Specify the paths
paths = [
'[default]D01/D01/Data/Database/Production/Produciton',
'[default]D02/D02/Data/Database/Production/Produciton'
]
# Send the reads off
values = system.tag.readBlocking(paths)
# Here we can examine each value
table = [values.value for values in values]
excelstr = system.dataset.dataSetToExcel(True,[table])
fileName = 'dump.xls'
system.perspective.download(fileName,excelstr)
I think 8.0.6 in particular had an issue with the excel functions. Latest 8.0.16 shouldn’t, if you can do a ‘minor’ upgrade before thanksgiving (8.0.17 should be out ~soon, too).
I would generally advise updating as often as possible to the most recent minor version. Obviously that isn’t practical in all scenarios, but the entire reason we’re continually releasing is to fix various bugs.
We take great pains to ensure upgrades work seamlessly, so there should not be any requirement (nor would I call it a best practice) to go to latest_minor before going to new_major.
So, as a non-answer - no, I wouldn’t say it’s advisable - but it doesn’t hurt anything to do it, either. As always, the key point of advice is to collect a .gwbk before doing any upgrading.