Joined Reports

Why Joined Reports Matter
Joined reports are a cornerstone topic in the Advanced Data and Analytics Management section of the Salesforce Advanced Administrator exam. They solve a real business problem: stakeholders frequently need to see data from multiple objects or multiple perspectives side by side in a single view, even when those objects do not share a direct parent-child relationship or when a standard report type cannot express the comparison. For example, a sales manager may want to see Opportunities, Cases, and Activities for the same set of Accounts on one report. Without joined reports, this would require several separate reports and manual reconciliation. Understanding when a joined report is the right tool, and when it is not, is exactly the kind of judgment the exam tests.

What Is a Joined Report?
A joined report is one of the four report formats in Salesforce (Tabular, Summary, Matrix, and Joined). It allows you to combine up to five report blocks in a single report. Each block functions like its own sub-report with its own report type, columns, filters, and sorting. Blocks are related to each other through a common field, typically the field shared across the report types in the join (for example, Account Name or Opportunity Owner). The blocks display side by side, with each block showing its own columns and summarized data.

Key characteristics to remember:
- A joined report can contain up to 5 blocks.
- Each block can use a different report type, but all report types must share at least one common object or common field to be joined.
- Each block has its own filters, so you can show, for example, Closed Won opportunities in one block and Open opportunities in another, both grouped by Account.
- You can add cross-block custom summary formulas that calculate across blocks (for example, Won Amount in Block 1 divided by Total Amount in Block 2 to get a win rate).
- Joined reports can be grouped by common fields, and groupings apply across all blocks.
- You can create charts on joined reports, but only one chart per report, and the chart must be based on groupings and summary fields common to the blocks.

How Joined Reports Work
1. Creating a Joined Report: In the Report Builder, start with any report type, then change the format to Joined. Salesforce converts the current report into the first block. You then click Add Block and choose another report type. Report types available for additional blocks are limited to those that share a common object with the existing blocks (Salesforce filters the list automatically).

2. Common Fields and Groupings: When you add a grouping, you are choosing a common field. The grouping is applied across all blocks, which is what creates the alignment in the display. For instance, grouping by Account Name shows each Account once, with its Opportunities in Block 1, Cases in Block 2, and Activities in Block 3.

3. Block-Level Settings: Each block has independent column selections, sort order, and filters. The row count, summary fields (Sum, Average, Min, Max), and even the record limit can differ between blocks. Renaming blocks is a best practice for readability.

4. Cross-Block Custom Summary Formulas: These are unique to joined reports. A cross-block formula references summary fields from multiple blocks using the block ID notation (such as B1#AMOUNT:SUM). They can only be placed at grand summary or grouping levels and only reference fields that are summarized.

5. Limitations You Must Know:
- Joined reports cannot be used as the source for dashboard components in Salesforce Classic. In Lightning Experience, joined reports can be used for dashboards, but only if the report has a chart, and the dashboard component will use that chart. This distinction is a frequent exam detail.
- Joined reports cannot be exported to Excel or CSV in the same way as other formats in Classic; in Lightning, export options are limited (formatted export only in newer releases, and details export is restricted).
- You cannot use bucket fields in joined reports.
- Joined reports cannot be scheduled for subscription with conditions in the same way as other formats (subscriptions are supported in Lightning but with restrictions on conditional alerts).
- Joined reports are not supported in the Salesforce mobile app for full functionality (they may display in a limited fashion depending on release).
- Only one chart is allowed per joined report.
- Joined reports cannot be used with report snapshots (analytic snapshots).
- Conditional formatting and some Lightning features such as row-level formulas are not available in joined reports.
- The performance of joined reports can be slower, and each block has a row limit of 2,000 records displayed.

Joined vs. Other Approaches
The exam often presents a scenario and asks you to choose the best reporting solution. Compare:
- Custom Report Type: Use when objects have a direct relationship (lookup or master-detail) and you need a single flat view with up to four levels of related objects. Supports dashboards, buckets, exports, and snapshots.
- Matrix Report: Use when you need to summarize one dataset by two dimensions (rows and columns).
- Joined Report: Use when you need to compare different datasets, different filters on the same object, or objects that are only indirectly related through a common field, all in one view.
- Dashboard: Use when you need several visualizations of different reports together but do not need row-level alignment.

Common Use Cases
- Compare Opportunities won this quarter versus last quarter for the same Owners.
- Show Accounts with their Open Cases, Open Opportunities, and recent Activities together.
- Display Campaign results from multiple Campaign Member statuses in separate blocks.
- Compute a win rate using a cross-block formula (Closed Won count divided by total Closed count).

Exam Tips: Answering Questions on Joined Reports
1. Look for the keyword clues. Phrases such as "side by side," "single report showing data from multiple report types," "compare different filters," or "objects that share a common field but no direct relationship" strongly point to a joined report.

2. Memorize the number five. A joined report supports a maximum of 5 blocks. If a question mentions needing six datasets, a joined report alone will not work.

3. Know the common-object rule. Report types can only be joined if they share a common object. If a scenario involves completely unrelated objects with no shared field, the correct answer is usually a custom report type redesign, a dashboard, or a data model change, not a joined report.

4. Remember the dashboard rule. In Lightning Experience, a joined report can feed a dashboard component only if it has a chart. In Classic, joined reports cannot be used on dashboards at all. Read the question carefully for which interface is referenced.

5. Eliminate based on limitations. If the requirement includes bucket fields, report snapshots, row-level formulas, or full export to CSV, a joined report is likely the wrong answer. Exam distractors often include a joined report as a tempting but incorrect option when one of these features is needed.

6. Cross-block formulas are the differentiator. When a question asks for a calculation that uses summary values from two different blocks (for example, a ratio between two different filtered datasets), the answer is a cross-block custom summary formula, which exists only in joined reports.

7. Distinguish from custom report types. If objects are directly related (parent-child) and the user wants a single flat list, a custom report type is the better and simpler answer. Joined reports shine when you need different filters on the same object or different report types aligned by a common field.

8. Watch for "one chart" questions. A joined report supports only one chart. If the question needs multiple visualizations, think dashboard instead.

9. Think about the user experience. Questions may ask how to make a joined report clearer; renaming blocks, applying consistent groupings, and keeping the number of columns per block small are best-practice answers.

10. Read every word of the scenario. The Advanced Administrator exam rewards precision. Note the number of datasets, whether they share a field, whether a dashboard is required, whether export is needed, and whether the environment is Classic or Lightning. These details decide between a joined report and an alternative.

Summary
Joined reports let administrators combine up to five blocks of data from related report types into a single view, aligned by common fields and enhanced by cross-block formulas. They are powerful for comparisons but come with notable limitations around dashboards (chart required in Lightning), bucket fields, snapshots, exports, and charts. For the exam, your job is to recognize the scenarios where joined reports are the ideal fit and, just as importantly, to recognize when a limitation makes them the wrong choice.