Warning We have announced the end of life of Jobserver and all related Jobserver integrations for September 30, 2024, with the exception of Public Sector customers using GovCloud or on-prem environments.
For information on registering a data source via Edge, go to Registering and synchronizing a data source via Edge.

Resolve a schema refresh conflict for a renamed column

If you refresh a schema where the data source contains a column that has been renamed, the ingestion process will detect a conflict. In the following example, the ingested schema contains a column that has been renamed.

Steps

1. Look up the new column with the search function or as follows:
   1. On the main toolbar, click , and then click Catalog.
      The Catalog Home opens.
   2. In the submenu, click Data Sources.
   3. Optionally, add the Refresh Conflict column to the table.
   4. In the table, expand the relevant schema and table to find the columns with refresh conflicts.

      

      

2. Select the updated column name and click Delete above the table.
   If necessary, select all column assets that are removed from the data source.
3. Click YesDelete to confirm the deletion of the column asset(s).
4. Double click the Refresh Conflict attribute of the renamed column.
5. In the Update Attribute dialog box, click .
6. Click Save.
7. Click the name of the original column.
   The column asset page appears.
8. Click Actions > Edit.
9. Change the name to the new ingested name.

   

   

10. Click Save.
11. Refresh the page.
    
12. Leave the column asset page open.
13. In the Refresh Conflict section of the column asset page, hover over the message and click on the right-hand side.
    
14. Click Yes to confirm the deletion of the attribute.
15. If necessary, repeat steps 4 to 12 for other renamed column assets.
    

What's next?

You can now safely refresh the schema with the new data source; however, keep in mind this may take some time.