paroney

Further Info - It can also crash in Firefox as well. If you artificially slow down your connections it fails. It appears to be the token that is the issue. The first iteration executes which loads a token, and then the second iteration overwrites that token, and so on. The token seems to be stored as a static / global variable, and so when the next request is made it uses the wrong token and fails.

Multiple reports (or charts) are displaying OK in Safari, Firefox, but not in Chrome. Sample script (below) returns an "unexpected.error" from within visualize.js when run on Chrome for the first report, but displays the second report correctly. It works perfectly on Safari and Firefox and displays both reports. Please do not suggest using differnt format script to produce multiple reports, as this format using multiple is required (as it is simultating our need for multiple discrete portlets that may be defined for a Liferay deployment). <script type='text/javascript'> window.onload=function() { visualize.config({ auth: { name: "jasperadmin", password: "jasperadmin" } }); visualize(function (v) { v("#container1").report({ resource: "/public/Samples/Reports/06g.ProfitDetailReport", error: function (err) { alert(err.message); } }); }); visualize(function (v) { v("#container2").report({ resource: "/public/Samples/Reports/State_Performance", error: function (err) { alert(err.message); } }); }); } </script> <script src="whetever..../jasperserver-pro/client/visualize.js?_opt=true"></script> <div id="container1"></div> <div id="container2"></div>

We have a report that is including an Excel Macro (using net.sf.jasperreports.export.xlsx.macro.template) and although it includes the macro code correctly, the file can only be created directly (via Jaspersoft or via Web Services Scheduling API to email) in a file with XLSX suffix. The file can be "saved as" an XLSM suffix file and the macro is avaialble, but is there a way to have it written directly to an XLSM file type?

Using a "Single Value" input control, with setting of Mandatory and Visible and a datatype of Text, and when used it always displays a default of "[Null]". Therefore when the control is used, the user always needs to delete the "[Null]" text and then enter a value. Running version 5.2.0. Our previous version 5.0.0 always (and preferrably) defaulted to an empty input control.