> ## 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/views/parameters/aliases",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# aliases

> Map old table names to updated table names to preserve content.

Creates an alias for a table, allowing you to ensure Omni content that uses the table doesn't break when the table is renamed.

## Syntax

```yaml theme={null}
aliases: [ OLD_TABLE_NAME ]
```

## Properties

<ParamField path="aliases" type="array">
  An array of old table names that should map to this view.
</ParamField>

## Examples

In this example, the `OLD_ORDER_ITEMS_NAME` table was renamed to `ORDER_ITEMS` in the database. Adding the original table name to the `aliases` parameter in the `ORDER_ITEMS.view` file in Omni prevents broken content and model validation errors.

```yaml title="ORDER_ITEMS.view file" theme={null}
schema: PUBLIC
table_name: ORDER_ITEMS
primary_key_sql: [ "${order_items.id}" ]
aliases: [OLD_ORDER_ITEMS_NAME]
```