Problem

If you meet a problem when you import a new Version of an application, in particular if you have an exception message about DuplicateId, Value [...] is not unique or key stolen, It means you make a modification on an object existing in the version to update and in the version used to update.

The main case is when you delete and create an object using the same name. This will lead to have an object using the same name but with a different ID.

Resolution

The Best way to avoid this issue is to avoid any modification in the version to update directly but using an export from the Dev environment.

If you need to delete and create a new version of an object, don't use the same Name. Because when you import the new version, the old version and the new version of the object will not share the same ID. This will lead to the Exception on duplicate ID (value not unique).

To solve this if it happen, compare the 2 versions and rename the object being change in the DEV and redo an export. You will have 2 versions in the updated application but this avoid the exception.

In some cases, the exception isn't help you to know which object need to be renamed. In this case only the Support could help you. Provide the 2 exports (update version and version to update). We will give you the objects impacted.

In future version (S1 2017), a suppression process will avoid the problem of ID.