I have two questions:
- (1) Is there any way to export the results of a query and send them as an attachment to a particular email ID?
- (2) Is there any way to schedule to get the report results and automatically send them in Excel to an email ID?
I have two questions:
We are currently using TRIRIGA 10.5.1/126.96.36.199. One of our user requests is to try and reduce the PDF size for an exported drawing from the Graphics tab. Of course, one way might be to hide a few of the layers before exporting. Apart from this, is there any other way to compress the file that is exported from the Graphics tab?
What would be the purpose of reducing the file size? (1) If you were expecting the export to run faster, that would not be possible except by turning off layers. TRIRIGA will process all the displayed graphic entities when generating the PDF. (2) If you want a smaller file size to make storage and transfer easy, then you can try using any third-party tool on the PDF file export after the fact. Note that I have no idea how compressible the graphic export is right now.
[Admin: To see other related posts, search “PDF Drawing“.]
I am designing a BIRT 4.5.0 report which has some images in it. While trying to export the report with the SpudSoft Excel Emitter, it results in an HTML page. My requirement is to export it into a multiple-sheet workbook. That’s why I went with SpudSoft. Any suggestions on how to get the Excel format via the SpudSoft option?
When exporting TRIRIGA records that contain text fields with carriage returns and line feeds, these fields will have extra spacing between the rows when viewed in the Excel spreadsheet.
The issue is that Excel treats CR+LF (\r\n\) as two separate line feeds. Some operating systems such as Windows use \r\n to represent a carriage return. The fix is to detect the existence of \r\n in a text string, and treat it as single line feed (\n) that Excel recognizes.
Moving forward, we resolved a query export-to-Excel issue, where each carriage return in an exported text field value was appearing in the Excel cell value as two new lines. The fix ensures that Excel cell values display each carriage return in a text field value as a single new line.
[Admin: To see other related posts, use the Excel tag.]
We can’t export the graphic floor map to PDF from TRIRIGA. The system is “hanging” and not exporting. This is only happening with some drawings and only occurs when using Layer 0 from the Xref file ( xrefdwg | 0 ). If all other layers are off and a layer zero from any Xref is displayed on the graphics section, even if empty, the export will fail to complete.
The export graphic was throwing a malformed XML exception. The root cause was that there was a “1 = 1” element that got pulled in from the layout of an attached Xref onto layer 0 on that Xref. It turns out that, for any text element that contains any equals sign, the process of sending the SVG from the client to server using a Dojo API to post via a hidden input element, resulted in extra double quotes getting sent, and causing the SVG XML to be malformed.
We resolved this by pre-processing the SVG sent to the server to remove these extra double quotes, before sending it to the SVG converter. Moving forward, the export graphic will now successfully export a graphics section that includes text that contains any equals sign. Text that contains both double quotes and equals in it, will get the double quotes removed for technical reasons.
With TRIRIGA 188.8.131.52 and BIRT 4.3.1 on Windows Server 2012 R2, we see that the “Export Report” option in a BIRT report defaults to “PostScript”, whereas in the current TRIRIGA 184.108.40.206 production version, it is defaulted to “Excel”. We want this export report option to be defaulted to “Excel” in TRIRIGA 220.127.116.11 as well. Only after upgrading from 18.104.22.168 to 22.214.171.124, we are seeing this change.
The BIRT engine did not sort the export options by default. Moving forward, the list of format options when exporting a BIRT report are now in alphabetical order, with the default being Excel XLS.
There are many installation scenarios that can cause TRIRIGA reports, especially BIRT reports, to fail to export due to timeout. Microsoft Excel exports are often the ones that you can observe because all of the file formatting happens during export.
Let’s focus on WebSphere Liberty installations, but this recommendation can be used for other web servers with some tweaks. Mostly, this is related to timeout settings, especially for HTTPS (SSL/TLS) connections. A good troubleshooting test is to perform the same action in a non-HTTPS (HTTP) connection. Does the report export? If so, take note of the time needed to export it and plan to extend the timeout in the HTTPS connection to at least double the time.
Refer to the IBM Knowledge Center > WebSphere Liberty > HTTP Endpoint topic. Look for the “sslOptions”, and also double-check the “httpOptions”, for timeouts.