Why do report calculations start before clicking the "View Report" button?

[and78386]

I've build a detailed report with some selection filters like date_from, date_to, product_from, product_to, output_type.

I've disabled the auto submit option for the report.

But Pentaho (bi-server-3.6-stable) seems to calculate the report before clicking on "View Report" and while selecting the filter parameters anyway. In the filter section i have to wait a few seconds before i can select the next filter field and Pentaho seems to calculate the result pages before "View Report".

How can i avoid this behaviour?

[and78386]

Still need some help here!

Reports are slow as hell because of the selection dialog which does a report recalculation every time when i change a selection field to another value.

What's wrong here?

[andrea]

Hi,
I've also noticed the same behavior! Number of pages is updated at each parameter's changes! Also when auto-submit is unchecked.... (3.6.0).
With large report is very annoying.

[richad3]

Hi,
As a workaround I use a CDF page to run my reports.
You can create a "Run Report" button that will actually work!!!!
You can create all the parameters that you need too...
Rich

[and78386]

Thanks for your CDF page suggestion, but is this problem not solvable without any workarounds? Or is this a behaviour "by design"?

(by the way: don't know anything about CDF page configurations for running reports; where can i find informations about such a workaround setup?)

[Taqua]

This is by design.

First, the "submit" button serves two purposes. It sends your data back to the server so that dependent parameters can refresh their value list properly and second it initiates the report processing to calculate the number of pages in the report. The page-count will only be run if all parameter validate correctly.

You can make the submit more explicit by simply adding an extra (mandatory) parameter to your report that must be selected before the report can run. Call it something like "Yes I am sure I want to see the report" and it will be clear to your users as well.

In 3.8, the reporting plugin got a bit smarter and as long as autosubmit is disabled, it now invokes a lightweight parameter-update request that does not perform any pagination if the parameter-refresh request was auto-generated (for instance by selecting a entry from a list-parameter).

[richad3]

If you have pentaho 3.7/3.8 you can see some example of the cdf possibilities for the prpt reports in the folder pentaho-solutions/bi-developer/ (just change visible to true in the index.xml to get it available in the user console)