dpetzold

In the main menu here you will see "Tracker". Select this and the "Create new Bug Report" hyperlink. This is very helpful as we are reviewing this.

You can use a special event ‘pageFinal’ which triggers when first page is ready. events: { pageFinal: function(el) { alert("Page is final!", el); } }, See the following example... http://jsfiddle.net/Suzfd/11/ With this the first page will show before all report pages are ready.

You could use the export function for Visualize.js and simply only have it run when some action (or paramater) is being passed into your embedded report. $(function() { $("#filterTen").on('click', function() { limitResults(10); });$("#filterReset").on('click', function() { resetFilters(); });$("#ExportButton").on('click', function() { slaveReport.export({ outputFormat: $("[data-paramId=exportFormat]").val() }, function(link) { var url = link.href ? link.href : link; window.location.href = url; }, function(error) { console.log(error); }); });});[/code]

You may want to enable logging to reveal more in the javascript console <script type='text/javascript' src="http://localhost:8080/jasperserver-pro/client/visualize.js?logLevel=debug"></script> Here's additional information on customizing your script with paramaters like this here... http://community.jaspersoft.com/wiki/visualizejs-api-notes-and-samples-v56

Yes, it certainly appears that Highcharts is being loaded twice here. Have you logged a case around this yet? I'm happy to look into this.

Are these tabs in a report or in your HTML? Usually tabs can only be seen one at a time in a page. I would be interested in more specfically how you are moving from one report to the next. Are they both on the same page? Any source files would be helpful as well.

While scheduling with Visualize.js directly is not yet available (REST services is the correct way today) you should be able to set predefined names for your reports and again, run Visualize.js to render the report at a set time. Since Visualize.js is a JavaScript library you have a host of ways you can control when and how the report renders in your page.

If the Visualize.js report changes after a few days (from the initial rendering) then you are going to need to rerun it again for it to render any changed information. Is there a particular reason you don't want it to re-run at a later time? You could code a function to either set a specific time or trigger by a method (action) to rerun this report and render it in your secondary page.

Are you currently seeing the image in your report when you view it in JRS? Any additional details, files, screenshots would be helpful.

In this fiddle you can see how hyperlinks should be implemented using Visualize.js. With this example, when you select from a city in the report it will open a secondary report below.

Keep in mind that all paramaters passed through Visualize.js start out in an array. Here is a fiddle showing the proper way to pass paramaters with multiple values. If they can't be hard coded you can pull them in dynamically using variables.

Are you simply trying to pass in comma seperated values similar to this fiddle? Where... params: { "ArrayName": ["Value1", "Value2"] },

You may want to try passing total row numbers with $V{REPORT_COUNT}. If this is translated into a passable parameter within Studio then it could be used within the Visualize.js framework to indicate the row count. Keep in mind that the variable scope starts after the query has been executed. If you can pass your calculation variable into a paramater it can then be easily passed into Visualize.js. In fact if you are only trying to discover if rows < 1 you can first do this calculation in a report variable and then pass a boolean paramater through Visualize.js to help aregister if the report has actual data. Perhaps something like this two step process will work to pass values from main report variables to a sub dataset through paramaters. 1) Create a paramater ($P{x}) in your sub dataset with the same data type as the variable ($V{y}) data type you want to pass. 2) In the report component (table, list, charts, etc) using the sub dataset, add the paramater in the sub dataset to pass the values $V{y} through $P{x}. Parameter: x Expression: $V{y} This will pass variable y to the sub dataset through its paramater x at run time when the report component is called.

There is report book pagination for reports. Is this part of what you are trying to accomplish? Perhaps you can provide more details around your specific use case. Visualize.js offers integration with pagination through anchors as you see in this fiddle. Additional fiddles around pagination can be found here.

Currently exporting a dashboard is enabled in the dashboard designer. You can follow these instructions for setting this up. In terms of direct exporting through Visualize.js, this feature is availble for reports but not yet available (as of this post) for dashboards.

In this case it would seem the variable is never updated when the element changes height, so it uses the 0px height it gets when the div is not yet visable. Here are a few possible solutions with Visualize.js today... 1. You could simply dynamically pull in each dashboard from an input control selection much like you see in the report "from a list" fiddle from the Visualize.js live samples guide. Simply create your own input control that is a set of tabs or buttons to dynamically load inside the same div rather then using multiple divs that are hidden. This will simulate similar behaviour. 2. You may want to set up seperate functions that are called (from the tabs) to essentially load each dashboard once the div is no longer hidden. 3. Or if you don't want to have to reload the dashboards at all (having them all load in the background) you could try an approach where the first dashboard is rendered in a div at the top of the page with a set of "tabs" or buttons to scroll down the page to the next div or dashboard with a similar set of controls. This vertical scroll trick may or may not work with your current design. There also may be some way to dynamically change the divs from visable to hidden allowing the dashboards to render beforehand. Something like... [DIV].style.visibility='visible' OR [DIV].style.visibility='hidden' Today it's not yet possible to render a dashboard accuretly through Visualize.js while a div is actively hidden.