Skip to main content
The table migration tool in the model IDE allows you to update table references within your Omni model when table names change on the database end, without breaking workbook queries, dashboards, or other model references that depend on the original table. This is ideal for situations where you are creating new versions of existing tables in your database.

​
Requirements

To follow the steps in this guide, you’ll need Modeler or Connection Admin permissions on the model you want to work with.

​
Migrating tables

1
In Omni, click Develop in the left navigation.
2
Click the model you want to work with.
3
In the model IDE, click Model > Branch to create a new branch.
4
In the model IDE, click Model > Migrate tables. The Table migration modal will display the tables you can migrate.The Migrate tables view in the Omni model IDE, showing a list of tables that can be migrated.
5
Locate the table you want to work with and click the Action dropdown to display the options.
  • Swap to a new table - Use when you have a replacement table ready to go. Updates references to this table throughout the model. When selected, a second dropdown will display. Use this field to select the table Omni should use as the replacement: The table migration modal showing the swap-to-new-table dropdown with available replacement tables. Swapping to a new table adds a renamed_from parameter to the table’s underlying view file, which helps prevent downstream references from breaking. In a view file, this will look like the following:
    View file with renamed_from parameter
  • Delete this view - Use when a table is no longer needed. Soft-deletes the table by adding ignored: true to the table’s underlying view file. If needed, you can recover the table by reverting the change in the Staged panel of the model IDE before merging your branch.
6
If needed, select actions for more tables in the modal.
7
When finished, click Migrate. This will apply the changes you made in the Table migration modal to your Omni branch.
8
Merge the Omni branch to promote the changes to the shared model. If the git integration is enabled for the model, you may need to open a pull request first.

​
After migrating

After merging your branch, use the Content Validator to verify that no downstream references were broken by the migration.
If your database schema has changed more broadly — such as new or removed tables and columns — use a schema refresh instead of or in addition to table migration.