---
title: "Renaming objects in your source and foreign key constraint errors"
canonical: "https://docs.vaultspeed.com/space/VPD/3320774983/Renaming%20objects%20in%20your%20source%20and%20foreign%20key%20constraint%20errors"
format: markdown
---
If you rename an object in your source and you re-import that object after the rename back into VaultSpeed, we will consider it as a new object.

This can lead to errors with the foreign key constraints to those objects that you are renaming.  A best practice is to first remove all of the constraints to the objects you will rename prior to re-importing their metadata into VaultSpeed.  The procedure would be:

- Create a new release in VaultSpeed, don’t import new metadata (make sure the Re-import source metadata slider is in the off position

![image](media://a0d10365-ccdc-4806-8737-62664aa8ceb5)

- Remove in the editor all relationships to the object you are going to rename
- Lock this source release
- Rename the object on the source
- Perform the 'Get Objects' task in the Select Objects menu.  Make sure you set the Selected Flag slider to yes for the newly imported renamed object
- Create a new release for you source, this time make sure the Re-import source metadata slides is set to the ON position
- If needed, re-draw the relationships to the renamed object and any other settings that are needed on that object.

> ℹ️ We are working on a feature that would let you map new objects to already existing ones from a previous release.  This feature would replace the above procedure, and all settings will automatically be taken over from the old object.