---
cuppy_hub: salesforce
cuppy_path: reference/official/data360/data-cloud-query-guide/guide/write-simple-query.md
cuppy_section: docs
cuppy_doc: CHHB-712E
cuppy_doc_uuid: c5f4fefc-fc5f-46d2-90c7-be97879224cc
cuppy_permalink: https://cuppy.io/salesforce/d/CHHB-712E
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/write-simple-query
cuppy_mcp: https://cuppy.io/mcp
cuppy_body_sha256: 904951dd44676ef10ca4348dd19d8e243a19c4912393116bfd68e65f67ca6a22
# 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/write-simple-query.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.

## Write a Simple Query

Let’s start with a simple query. View all individual customer records with a query that selects all fields from `ssot__Individual__dlm` DMO.

The `SELECT` clause uses the asterisk (*) wildcard character to get all fields from `ssot__Individual__dlm`.

To specify a subset of fields to retrieve, list the field names in the `SELECT` clause. To specify the type of object to retrieve the details from, use the `FROM` clause.

For example, this query retrieves only the first name, last name, the individual’s ID, and the key qualifier (`KQ_Id__c`).

This query output shows sample results.

| `ssot__FirstName__c` | `ssot__LastName__c` | `ssot__Id__c` | `KQ_Id__c` |
| --- | --- | --- | --- |
| `Phyllis` | `Cotton` | `00QHu00003W7JIAMA3` | `CRM` |
| `John` | `Bond` | `003Hu00003SELnCIAX` | `CRM` |
| `Mike` | `Braund` | `00QHu00003W7JICMA3` | `CRM` |

What’s the key qualifier (`KQ_Id__c`)? Data ingested from different data sources can result in records having duplicate IDs. In our example query, the `ssot__Id__c` column sometimes contains duplicates. The key qualifier, combined with the record ID, uniquely identifies each record. Together, the key `ssot__Id__c` and the key qualifier `KQ_Id__c` form the unique, fully qualified key. To make sure that joins in Data 360 are correct, perform all joins on both the Id and the key qualifier columns. See [Data Interpretation with Fully Qualified Keys](https://help.salesforce.com/s/articleView?id=data.c360_a_data_inter_fqk.htm&type=5) in _Salesforce Help_.

Now let’s view a calculated insight with its measure field and dimension field.

For example, say we have a calculated insight that computes the number of contact point addresses for each unified individual. The insight has a measure of `count1__c` and a dimension of `ind_id__c`, which is the ID of the Individual DMO. The query results for this calculated insight are similar to this output.

| `count1__c` | `ind_id__c` |
| --- | --- |
| `1` | `8608b9f028a77452a4c434ec97ea96bd` |
| `2` | `864d017d1c4b3fe454cc5b8eab6420bc` |
| `1` | `903c9f06924bcb170bf3c896ead0656d` |


---
<!-- 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 -->