---
schema_version: "1"
id: 3669ab51a077729db4069fabaaa164535e71c73cc33ef9ddc6fb80957f5c98d3
title: Considerations for Joined Reports in Data 360 Reports
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/analytics/264-0-0/rd_dc_reports_joined_reports_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=analytics.rd_dc_reports_joined_reports_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a35c8944e6eaae13e60f826babb0cd1a7d737010ab7495beaf5e1381a7a07b1a
description: Keep these considerations in mind when working with joined reports in Data 360 reports.
products:
  - Cross Cloud
release: "264"
---
# Considerations for Joined Reports in Data 360 Reports

Keep these considerations in mind when working with joined reports in Data 360 reports.

- Joined reports support only Data Model Objects (DMOs) as report sources. Calculated Insight Objects and Semantic Data Models aren't supported.
- Every report block must share at least one common field with the base block.
- You can group across report blocks only by a field that's common to all active blocks. Fields that aren't common to all blocks can be added as columns in the blocks where they're available.
- Joined reports in Data 360 reports are supported only in Lightning Experience. Salesforce Classic isn't supported.
- Joined reports in Data 360 have the same limits as joined reports in Lightning reports. For more information, see [Joined Report Limits, Limitations, and Allocations](https://help.salesforce.com/s/articleView?id=analytics.reports_unavailable_with_joined_reports.htm&language=en_US)