---
cuppy_hub: salesforce
cuppy_path: reference/official/data360/data-cloud-query-guide/guide/dc-soql.md
cuppy_section: docs
cuppy_doc: HA5X-11AQ
cuppy_doc_uuid: b368e23c-c71f-425f-b352-c17b8242f6d9
cuppy_permalink: https://cuppy.io/salesforce/d/HA5X-11AQ
cuppy_version: 1
cuppy_updated: 2026-10-23T16:16:52.575Z
cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/data-cloud-query-guide/guide/dc-soql
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 3b016a4cb598bb9b801e1b341e576b7c18e9e860ed0e86cc3bafc9843df33464
# cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks.
---

> Mirror of <https://developer.salesforce.com/docs/data/data-cloud-query-guide/guide/dc-soql.html> (Salesforce, Data 360 Query Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers.

## Using the Salesforce Object Query Language (SOQL) to Query Data in Data 360

Similar to how you use SOQL to query Salesforce objects, you can also use SOQL to query Data 360 objects, such as DLOs and DMOs, with some limitations. SOQL is Salesforce’s proprietary query language to query Salesforce objects. You can run SOQL in Apex or by using tools such as the Query Editor and SOQL Builder.

To learn about querying DMOs in Apex with SOQL, see [Data 360 in Apex](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/DataCloudInApex.htm) in the _Apex Developer Guide_. Also see [Mock SOQL Tests for Data 360 Data Model Objects](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/MockSOQLTestsForDMOs.htm) in the _Apex Developer Guide_.

SOQL is similar to SQL, but here are a few differences between the two.

*   SOQL statements can execute in Apex on the Salesforce Platform, and not only using an API.
*   SOQL doesn’t support the asterisk (`*`) character to retrieve all fields in the `SELECT` statement. To retrieve all fields, use the `FIELDS(ALL)` keyword or retrieve specific fields.
*   SOQL provides parent and child relationships instead of `JOIN` statements. These relationships aren’t supported in the current implementation of SOQL in Data 360.

For the SOQL language reference, see [_Salesforce Object Query Language (SOQL)_](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm). To learn about the use of SOQL in general with Salesforce objects, see the [_SOQL for Admins_](https://trailhead.salesforce.com/content/learn/modules/soql-for-admins) Trailhead module.

**See Also**

*   [_SOQL and SOSL Reference_: SOQL Object Limits and Limitations](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_limits.htm)
*   [_Apex Developer Guide_: SOQL and SOSL Queries](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/langCon_apex_SOQL.htm)
*   [_Salesforce Help_: Developer Console](https://help.salesforce.com/s/articleView?id=code_dev_console.htm&type=5)
*   [_Salesforce Extensions for Visual Studio Code_: SOQL Builder](https://developer.salesforce.com/docs/platform/sfvscode-extensions/guide/soql-builder.html)
*   [Data 360 Object-Specific APIs](https://developer.salesforce.com/docs/data/data-cloud-query-guide/guide/obj-specific-apis.html)


---
<!-- cuppy -->
You are reading one file. The same content is free over MCP at https://cuppy.io/mcp with no signup: ranked search across all 376 documents in this hub, the merged view when you work in a layer, known workarounds matched to the error you hit, and depth control so you spend tokens on what you need. Start with the `_hello` tool. How to connect: https://cuppy.io/salesforce/ Something wrong in this document? Report it with the `session feedback` tool on the same endpoint.
<!-- /cuppy -->