Inline Aggregate Reporting

Inline aggregate reporting lets you insert columns in custom reports to show aggregate information that could not normally display due to restraints on database query size.

The aggregate data you want displayed in a column is compiled in a separate report and then pulled into a column in the primary report. This breaks the database query that would normally be required to return the data in a single report into multiple queries from multiple reports.

Note: You can pull data from several reports into columns in a single parent report. However, the parent report cannot have more than 500 cells displaying inline aggregate data.

Using this feature helps avoid query limitations when running reports that include summaries of data from tables containing large amounts of data, such as transactions or incident performance, particularly when joins do not exist between all the tables you need to include in a report.

Caution: Using inline aggregate reporting is not recommended for most reports where normal inner or outer joins are used, since it will result in less efficient reports that may not run successfully. Use inline aggregate reporting only when the query required to return aggregate data in a column results in a Cartesian join between tables. This is when data is pulled from all rows in the tables required by the query, resulting in a large number of rows being accessed. If you’re unfamiliar with Cartesian joins, or have questions about whether using this feature will help a report run more efficiently, please submit a service request.