AAM Reports are the middle man between Data Sets and Dashboards. Data sets are where data is warehoused. Reports turn that data into visualizations. And finally Dashboards display the visualizations in a convenient and digestible layout. Each Report is tied to exactly one data set. You then build all the visualizations you need from that data set in the report. There are many types of visualizations available. From pivot tables all the way to geocharts. We won't be getting into the details on how to build each type of visualization. For that, please see the BellaDati documentation found here - http://support.belladati.com/doc/Reports. This page gives you an overview of reports, permissions, and how to start using them.
To begin, remember that reports are not meant to be the consumable part of AAM. Dashboards are used for that. So you don't necessarily need to tweak the layout of reports to be perfect. Probably only one or a small handful of people will look at reports directly anyways. In general, you'll probably only have a few report managers in your entire organization. These report managers are responsible for building and maintaining your visualizations.
To reach the Reports area of AAM go to Topics | Advanced Analytics | Reports. Or point your browser to https://aam.projectorpsa.com/en/bi/search/$N/true.
Permissions and Settings
A user with the Report Editor role can:
- Create new reports
- Edit reports they own
- Edit reports shared to them
- Delete reports they own
Your AAM administrator can delete or edit any report in the system.
Each Report is tied to exactly one Data Set. If you need to create a report that contains data from two or more data sets, you'll need to either perform a join of the data, or use the CrossValue function instead.
Because Reports are tied to one Data Set - editors need to have data sets shared to them (or own them outright) in order to build anything. In general, your report editors should also be data set managers.
Limiting data access - you can apply filters both on a per-report basis and per-view basis. When data is limited at the report level, it affects all views. You can optionally create a view of type "filter" on the report that provides interactivity with the displayed data. You can also apply filters on each individual view. When you apply filters at this level, there is no option for interactivity for the report consumer.
A report can be shared to other AAM users as either read-only or as editable.
The basics of managing your reports.
Visit a data set. On the landing page click Create report.
Visit an existing report and choose Edit | Copy Report.
Visit a report and click Edit | Content and Layout.
Visit a report and click Edit | Remove.
When you visit a report, the following menu bar is shown. This section explains what is possible via the menu bar.
Under the edit menu you have the following options:
- Content and Layout - add visualizations, edit existing visualizations, and customize the layout.
- Settings -
- Copy report -
- Appearance -
- Remove -
Share the report with other users or user groups. Those users can optionally edit the report too.
Export a backup of your report as XML.
Variables and Filters
Limit the displayed data based on filters you create. The filters affect all views throughout the report.
Comments and Attachments
You can attach reference files or make comments about this report. Useful for keeping an audit trail of why changes were made. Comments cannot be edited, but they can be deleted.
Each time a report is saved, a history row is added. You can click on any history row to restore that version of the dashboard. When you do this, you can optionally resave the displayed view and it becomes the most recent historical version.
As mentioned in the introduction, this help page does not get into the details of creating visualizations. Rather, you should visit the full BellaDati documentation found at http://support.belladati.com/doc/Reports.