Summary
This article describes how to load reports.
Table of Contents
- Loading a Report
- Loading a Previously Loaded Report
- Loading Union and Package Reports
- Loading Reports with Different Permissions
Any role enabled with Admin access to Ad Hoc Reports has the ability to load an existing report from one cluster (Design, Test, Approve, Production) to another. For example, a report that has been built, reviewed, and accepted for a study in Approve can be loaded to Production (Live environment) when the study has deployed.
Loading a Report
- Access the Ad-Hoc Reports page by opening the navigation menu , clicking on Reports, and then selecting Ad-Hoc Reports.
- On the Reports page, hover over the Actions menu and select Load Report.
- The Load Report from a Different Cluster screen will display. First select the cluster from which you would like to load report. For example, select Approve to view the available reports in the Approve Environment.
- Select the check box next to the report to load.
- The report will load and appear in the list of available reports for your current environment.
- The report description (viewable by clicking the icon) will indicate that the report was loaded form another environment.
Loading a Previously Loaded Report
When loading a report, any report that has been previously loaded will be indicated with . Reloading the report will update the report to the latest configuration.
Loading Union and Package Reports
Loading Union and Package reports will also load the individual component reports that comprise the Union or Package.
In the even that a reloaded component report doesn’t match the Union report structure, the ‘run’ icon for the Union report will be disabled, and a tooltip will indicate the reports must have matching structure.
Loading Reports with Different Permissions
When loading a report that contains report permissions for roles that do not exist on the cluster (No common roles) the report will be view-able for all roles until Permissions are set on the cluster. If a report is loaded that has permissions for roles that do exist in both clusters and all roles in the cluster it is loading into do not contain permissions to view the report, no role will be able to see the report. You will need to update the permissions to allow at least one row on that cluster to view it
Need more help?
Please visit the Fountayn Contact Information page.