Skip to content

Commit 4a01f38

Browse files
committed
Remove comments
1 parent 963c5e6 commit 4a01f38

File tree

1 file changed

+2
-14
lines changed

1 file changed

+2
-14
lines changed

src/unify/linked-profiles/data-graph.md

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,7 @@ To use the Data Graph, you'll need the following:
1717
- A Unify and Engage Foundations or Premier plan.
1818
- A Snowflake Data Warehouse.
1919
- [Profiles Sync](/docs/unify/profiles-sync/) set up with ready to use [data models and tables](/docs/unify/profiles-sync/tables/) in your warehouse.
20-
- An [Actions-based Destination](/docs/connections/destinations/actions/#available-actions-based-destinations)
21-
- A Braze, Customer.io, or Iterable Destination. <!-- are we supporting all destination actions here? -->
20+
- An [Actions-based Destination](/docs/connections/destinations/actions/#available-actions-based-destinations).
2221

2322

2423
> info ""
@@ -143,10 +142,6 @@ Use the following relationship, parameters, and examples to help you relate enti
143142
| `name` | This should be a unique label that displays throughout your Segment space. |
144143
| ``related_entity` | Reference your already defined entity. |
145144

146-
<!-- remove
147-
- `relationship`: A unique slug for the relationship, which is immutable and treated as a delete if you make changes. The slug must be in all lowercase and will support dashes or underscores (for example, `user-account` or `user_account`).
148-
- `name`: This should be a unique label that displays throughout your Segment space.
149-
- `related_entity`: Reference your already defined entity. -->
150145

151146
A profile can be related to an entity in two ways:
152147
1. With an `external_id`: Define the external ID that will be used to join the profile with your entity.
@@ -197,13 +192,6 @@ data_graph {
197192
| `related_entity` | Reference your already defined entity. |
198193
| `join_on` | Define relationships between two entity tables `[lefty entity name].[column name] = [right entity name].[column name]`. Note that the entity name is a reference to the alias provided in the config and doesn't need to be the fully qualified table name. |
199194

200-
<!-- remove
201-
- `relationship`: A unique slug for the relationship, which is immutable and treated as a delete if you make changes. The slug must be in all lowercase and will support dashes or underscores (for example, `user-account` or `user_account`).
202-
- `name`: A unique label that displays athroughout your Segment space.
203-
- `related_entity`: Reference the slug of your already defined entity.
204-
- `join_on`: Define relationships between two entity tables `[lefty entity name].[column name] = [right entity name].[column name]`.
205-
- Note that the entity name is a reference to the alias provided in the config and doesn't need to be the fully qualified table name.
206-
-->
207195

208196
```py
209197
data_graph {
@@ -325,7 +313,7 @@ data_graph {
325313

326314
Validate your Data Graph using the config builder and preview, then click **Save**.
327315

328-
## Editing your Data Graph
316+
## Edit your Data Graph
329317

330318
To edit your Data Graph:
331319

0 commit comments

Comments
 (0)