I assume you're getting timeouts when trying to export such reports -- have you tried turning off Format Column and Row Size? That can lead to considerably shorter running times; besides, while it wouldn't look exactly like before turning that option off, it wouldn't be raw data as in CSV, either.
Its not a time out, Helix ITSM runs ok (Bit slow, but no timeout). It's more that it produces a file that is to big for Excel to use.
Obviously this is a waste of peoples time when they run the large report, finally get the output, only to find that they can't do anything with it.
What I was wondering was if there was a way for Smart Reporting to suggest that a file may be too big to the user.
is this more an Excel problem related to memory on the user machine that is stopping the file from being opened, as you say it is created but Excel cannot open it?
I don't believe there is a particular way of configuring the output size, so you would need to raise an idea for a potential setting that can be configured to limit the size of the resulting file.
1 of 1 people found this helpful
From your initial description, it sounded like an exporting problem with Smart Reporting, but this describes it as importing problem with MS Excel. You could add warning about possible size issue to report's description (which would end up in exported report so it may not be desirable), or add mandatory filter which would require confirmation that consumer realizes exporting such report into XLSX may cause issues in Excel before running report (it would have to be blank by default and possibly prevented from remembering previous selections).
3 of 3 people found this helpful
In addition to the inputs received, below listed one's that you can consider:
1. Straight forward approach, take away the permissions to 'Export Reports/Dashboards to 'Excel' for the role assigned to the users and give them access to only 'Export Reports to CSV'. If the trend of creating large reports continues.
3. There is a need to educate Report Users to optimize the output and not to generate large reports. Since it is evident that it will create large Excel reports when you export. You may refer below:
Finally, there isn't any automated way that Warn/Caution the user that the Export To Excel will generate a file size of xx.MB. In fact I have considered a way to change the in-built Info/Warning/Error messages that can help here; however, that doesn't seems to be so very easy! :-(
Info: You can change all the error/warning messages displayed in SmartReporting via the ApplicationResources.Properties file. :-)
Hope this helps!
ad 2. Those may not be duplicate records, only not quite grouped ones -- e. g. first ten records could have identical values in column #1 (Conrad doesn't want to have it displayed ten times so he selects suppress duplicates in column's definition -- the same goes for nineteen other columns) but their values in other columns may differ so records aren't duplicate.
I do think it's more about Excel then Smart Reporting. Just wanted a way to limit the outgoing file size
Thanks Ravi. Think I will have to limit people to CSV reports until we can sort the large file size notification issues in some other way.
Thank you to everyone who has replied to this one.