If you are unable to create a new account, please email support@bspsoftware.com

 

"Save as report view": change the default properties

Started by Sunchaser, 11 Oct 2024 08:46:49 AM

Previous topic - Next topic

Sunchaser

Hi all,
When running a report, it is possible for a user to do "Save as report view".
In theory, perfect functionality.
Unfortunately, in this case, the report view in the case has for property "View the most recent report" in Properties / Report / More options / Default portal action.
This is a bit of a "disaster", as this behavior is not understandable for my users.
Question: is it possible to change definitely this default property in this case ? In other to have per default "Run the report".
Thanks!
Vinc

dougp

If you want users to run the report against the data source every time, don't save a static copy of the report.

Sunchaser

Hello dougp,

Thanks, but this is not helping.
If the setting is on "View the most recent report", then only the last "version of the report" is displayed, which is not what we want here.
All my report views are set with:
. "Run the report" (and not "View the most recent report")
. Run the prompt page = 'No'
. A set of pre-defined values for each prompts in the prompt page.

Based on this, when they click on the link of a report, they get a report with "fresh" data, based on the set of pre-selected filters without having to enter them manually each time (this is not what they want to do).
Glad if you have another way to do this.

Thanks
Vinc

dougp

The problem you describe only happens if there is a last version of the report.  So it is not necessary unless someone mistakenly saved report output with the report view.  You should identify why there is a static output saved there and deal with that first.  If you have a report view that is being used both for interactive reporting and for running on a schedule, there are two options to get the result you want:  Manually set the "Default portal action" to "Run the report" or separate the two functions (interactive vs. scheduled) into separate report views.

My guess is that the user ran the report, was viewing the output, and saved a report view from there.  After performing that action, they should probably go back to Content, right-click on the report view, view versions, and delete the saved output.  (I actually ran into a similar situation just yesterday.  A user had saved a report while viewing it.  The report was their responsibility so they had permission to save there.  Yesterday they contacted me wondering why the output hadn't changed since September 2023.)  Or they should have created the report view from the actions view in Content.  Either way, it seems like the user needs some training.  If the existence of the reporting system saves the user hours or days of workload during a year, they can spend a few minutes to learn how to use it.