Resolve a schema refresh conflict for a renamed table
If you refresh a schema where the data source contains a table that has been renamed, the ingestion process detects a conflict.
In the following example, the original schema Refresh contains the table firsttable. This table has been renamed to firsttable2. After refreshing the schema, refresh conflicts appear, as shown in the following image: 
You have to manually resolve the conflicts before you continue. It is not possible to refresh a schema when there are conflicts.
Note You have to add the Refresh Conflict column to the table if it is not there already.
Steps
-
In the main menu, click
, then
Catalog.
The Catalog Home opens.
The Catalog Home appears - In the submenu, click Data Sources.
- Expand the tables to see all the columns that are contained in them.
- Select the renamed table and all its contained columns, in this example, firsttable2.
- Above the table, click Delete.

- Click Yes to confirm the deletion.
- Hover over the original table, in this example, firsttable, and click
to the right of the table name. - Change the name to the new ingested table name, in this example, firsttable2, and click
to apply the change.
- Hover over a column contained in the table you just renamed and click
to the right of the column name. - Rename the column by replacing the table part of the name with that of the renamed table and click
to apply the change.
The column name is a concatenation of the table name and the original column name and so you just have to replace the table part of the name with the new table name. For example, to rename the column name firsttable > column1 to firsttable2 > column1, you just have to change firsttable to firsttable2 so that the column name becomes firsttable2 > column1. - Repeat this action for all the columns in the renamed table.
Now, you only see the new ingested table, firsttable2, and the columns contained in the table.
- Click the name of the renamed table.
The table asset page appears. - In the Refresh Conflict section, hover over the refresh conflict message and click
on the right-hand side.
- Click Yes to confirm the deletion of the Refresh Conflict attribute.
What's next?
You can now safely refresh the schema with the data source.