> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omni.co/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/modeling/relationships/parameters/id",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# id

> Omni-generated identifier for duplicate joins.

The `id` parameter is added when Omni has detected duplicate joins in your model. This identifier helps distinguish between multiple joins to the same table, but its presence typically indicates that your model needs attention.

<Warning>
  Rather than using this parameter explicitly, you should review your join relationships and eliminate any unnecessary duplicates.
</Warning>

## Syntax

```yaml theme={null}
id: <identifier>
```

## Properties

<ParamField path="id" type="string">
  An identifier Omni adds to relationships when duplicate joins are detected. Avoid explicit use.
</ParamField>

## Examples

```yaml title="Duplicate joins for buyers to buyer_facts" theme={null}
- id: buyers_0
  join_from_view: buyers
  join_to_view: user_facts
  join_to_view_as: buyer_facts
  join_type: always_left
  on_sql: ${buyers.id} = ${buyer_facts.id}
  relationship_type: one_to_one

- id: buyers_1
  join_from_view: buyers
  join_to_view: user_facts
  join_to_view_as: buyer_facts
  join_type: always_left
  on_sql: ${buyers.id} = ${buyer_facts.id}
  relationship_type: one_to_one
```