We are trying to update custom metadata records via deployment from source org (Dev Sandbox) to target (i.e. Packaging environment - Dev Edition), these records were packaged into a managed release in the target environment in the past. Below error occurs during the deployment:
Developer name already exists for given entity or has been previously used. Please choose a different name.
- For example, initially the custom metadata data record was deployed with name
- Later during a round of deployment the same error occurred, as a work-around to the deployment error it was renamed to
A_xyzjust in the target environment. (not in source environment) The record was not packaged at that time.
- Currently, when we try to deploy the same record with the original name as
Acc_xyz(same as source org) which does not exist in the target org, it breaks the deployment and throws the error mentioned above.
- Because the existing custom metadata records in the target org are packaged, their name is not editable or the record is not deletable. So, clean-up can't be done in the target org as well.
There are around 250-300 custom metadata records which need to be updated and also the number can grow in future. So, it would not be feasible to update the records manually in the meta file directly by keeping the same name.
This issue blocking the package creation/release. Appreciate any help/possible solution on how to go around this issue, Thanks!