> ## 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/join-to-view-as-label",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# join_to_view_as_label

> Controls the display name of the joined view in the UI when using the join.

For example, you might want fields from `user_facts` to appear as if they belong to the `buyers` table. In reality, the fields come from `user_facts`, which is aliased in the model and generated in SQL as `buyer_facts`.

This can be used jointly with [`join_to_view_as`](/modeling/relationships/parameters/join-to-view-as) or used as a way to label a view within a topic.

## Syntax

```yaml theme={null}
join_to_view_as_label: <display_label> 
```

## Properties

<ParamField path="join_to_view_as_label" type="string">
  The display name for the joined view in the UI.
</ParamField>

## Examples

```yaml title="Label the buyer_facts view as Buyers in the UI" highlight={4} theme={null}
- join_from_view: buyers
  join_to_view: user_facts
  join_to_view_as: buyer_facts
  join_to_view_as_label: Buyers
  join_type: always_left
  on_sql: ${buyers.id} = ${buyer_facts.id}
  relationship_type: one_to_one
```