What is Multi-Pass Reporting?

Multi-Pass Reporting is an advanced reporting tool enhancing the flexibility and scalability of data analysis across multiple objects. Some key benefits include:

  • Combining data across multiple report views into one report

  • Manual configuration of join fields for data integration

  • Multi-level relationships for comprehensive reporting, for example, pull in a grandparent and/or child object

  • Automatically applies left joins between report views, meaning all records from the primary report are included to ensure all relevant data is presented even if there aren’t matching records

  • Scale to more complex reporting scenarios without having to create multiple reports or rely on manual data merges, making it easier to generate reports on large data sets and across multiple objects

Learn more about Multi-Pass Reporting.

How can Multiple Reports be Joined?

When creating a Multi-Pass Report Type, define how the data connects across report views. Vault CRM offers several join options to control what records display, and how.

  • Left Join - Retains all primary report records

  • Inner Join - Only includes matching records

  • Custom Join - Includes records via flexible field-based connections

  • Multi-Step Join - Connect multiple reports to establish a connection between otherwise unrelated records

Left Join (Default Join Type)

A Left Join includes all records from the primary report view, even if there isn’t any matching data in the second, joined report view. This is useful when you want to retain all records from the first report, but only include matching records from the second report.

For example, consider the primary report, Document, joined via Left Join to the secondary report, RV Account. Even if a Document doesn’t include an RV Account, all Document data still displays in the final report. RV Account data only displays if there is corresponding data to the primary report.

Inner Join

An Inner Join only includes records where there is a match in the primary and secondary report. If a record exists in the first report but doesn’t have any corresponding data in the second, the data is not included in the final report.

For example, consider the primary report, Document, joined via an Inner Join to the secondary report, RV Account. Only data with corresponding matches from both reports displays in the final report, in this case, Documents with RV Accounts are displayed.

Custom Join

A Custom Join enables users to define the field on which reports are joined. The join can be based on any field with matching data types, for example, text, number, and date fields.

Multi-Step Join (Daisy-Chaining)

Multi-Step Joins allow multiple reports to be joined in a sequence to work around Vault CRM’s report type limitations. Instead of a direct join, data is linked through an intermediary Report View.

For example, consider the reports, Accounts, Calls, and Key Messages. The organization wants to understand the rate at which accounts segmented on a target product metric are receiving Key Messages.

By using a Multi-Step Join, the company can connect multiple reports to create a link between the Accounts and Key Messages report:

  1. Join the Accounts report to the Calls report.

  2. Join the Calls report in the Key Messages report.

This creates a Multi-Pass Report providing the organization with a single report spanning the three objects.

Select Next to learn about dashboards.