- A tabular report
- A chart-based report
- A simple pivot report
- A report with parameters
First, we reviewed the following design elements and showed how they help to enable self-service reporting for end users.
- Minimalistic menu ribbon
- Simplified property panel
- Readily available toolbox
- Auto-hidden panels
These design elements combine to ensure that we dedicate as much of the available space as possible to the report design surface.
This WYSIWYG web designer brings the power of reporting to the end user in a way that is not overwhelming. While it hides the advanced functionality from the common user, report authors and power users can use the Show More button to see all of the properties that developers see in RDL reports. This enables them to design pixel-perfect reports right in the browser window.
Other aspects of self-service reporting that the designer addresses include:
- Prepared datasets for data governance
- Themes and styles for organization-wide reporting consistency
- Expressions for ad-hoc calculations and conditional formatting
- Data aggregation to find relationships between disparate data sources
With the theory covered, we did a deep dive into the steps to design a tabular report. We used a shared data set to show a list of customer orders.
For the chart-based report, we used a data set showing sales by region. We uncovered the relationship between profit and quantity sold to determine the performance of stores.
The third report was a more complex pivot. We showed details of the average sales price for all movies by media type.
Then we added a country parameter to the Customer Orders report. We also discussed how to create an ad-hoc data set based on a direct query, and how to limit its use to the current report.
Here is a recording of the session if you would like to see the report design process.