--- cuppy_hub: salesforce cuppy_path: reference/official/data360/connectapi/guide/features_cdp_dbt_validations.md cuppy_section: docs cuppy_doc: GR6V-HSG4 cuppy_doc_uuid: e3154a77-42d7-4487-a22f-cd3fa0985667 cuppy_permalink: https://cuppy.io/salesforce/d/GR6V-HSG4 cuppy_version: 1 cuppy_updated: 2026-10-23T16:16:52.575Z cuppy_canonical: https://cuppy.io/salesforce/docs/reference/official/data360/connectapi/guide/features_cdp_dbt_validations cuppy_mcp: https://cuppy.io/mcp cuppy_body_sha256: d6d962e76aaf5e7027996efba6ba31aaaae1794d946fd069a34095cf1fc25351 # cuppy_body_sha256 is over the document body ALONE, excluding both generated blocks. --- > Mirror of (Salesforce, Data 360 Connect REST API Guide), read 2026-10-23. Salesforce's own page is the authority; this copy exists because that site refuses non-browser readers. ## Supported Validations for DBT Segments To create a segment, use the [POST `/ssot/segments`](https://developer.salesforce.com/docs/data/connectapi/references/spec?meta=createSegment) endpoint. To update a segment, use the [PATCH `/ssot/segments/{segmentApiName}`](https://developer.salesforce.com/docs/data/connectapi/references/spec?meta=updateSegment) endpoint. When creating or updating a segment, the `sql` property is subject to these validations. * Only the primary key of the SegmentOn DMO is allowed in the `select` statement. The first table in the join clause must be a profile table. * No aggregation (min, max, avg, count) is allowed at the top-level select. * No select all (*) expression is allowed in the top-level select. * Only the primary key of the segment on table (the first table in the `from` clause of the sql statement) can be selected. * Multiple columns can’t be selected even if one of them is the primary key of the table. * No `case` statements are allowed in the primary `select`. * If the primary key of the `segmentOn` object has key qualifiers, you must project the key qualifiers, as well, in the primary `select`. First project the primary key and then the qualifier. Group bys must also include the key qualifiers. * If the primary key of the `segmentOn` object has key qualifiers, you can provide an additional condition in the join on condition. * All columns must be fully qualified by table name in the query and subselect queries. * Subqueries are supported only in a `where` clause and must emit only one column. * Compare columns of the same data type. To compare columns of different data types, cast one or both of the operands so that they have the same type. * `limit` and `offset` are supported. * Any SQL statement other than the `select` statement isn’t allowed. * Aliases are not supported. * To join two DMOs, there must be a relationship between the DMOs, and you must use one of their related join keys in the join on condition. The join on condition can contain only an equality comparison between the joining keys and an optional additional condition for comparing FQK fields. --- 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.