Take the 2-minute tour ×
Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

When I try to redeploy an object that exists in source and destination orgs, the deploy fails with the cryptic and useless error message:

duplicate value found <unknown> duplicates value on record with id: <unknown>

This fails whether I deploy with Migration Tool or IDE. Note, individual fields are deployable, but not the object.

share|improve this question
    
Figured out the problem. Some Salesforce issue with History tracking was the root cause. Turned off history tracking in dest org and once the history object was eliminated, the object could once again be deployed. Not sure why there was an issue, though the object label was changed in the source org. I think SFDC was trying to recreate the History Object during the object deploy. I would have to say there's an underlying Salesforce Bug that should be resolved here, but a 2 minute workaround is better than the full day lost having to go through their support process. – DaveS –  Mohith Shrivastava Jan 8 '13 at 18:48
    
You can go ahead and make this answer and self make it correct so it helps others.Thanks –  Mohith Shrivastava Jan 8 '13 at 18:49
add comment

2 Answers 2

up vote 8 down vote accepted

Figured out the problem. Some Salesforce issue with History tracking was the root cause. Turned off history tracking in dest org and once the history object was eliminated, the object could once again be deployed.

Not sure why there was an issue, though the object label was changed in the source org. I think SFDC was trying to recreate the History Object during the object deploy. I would have to say there's an underlying Salesforce Bug that should be resolved here, but a 2 minute workaround is better than the full day lost having to go through their support process.

share|improve this answer
    
Please accept your own answer then so it goes off the radar ;) We need to keep the statistics nice so this site leaves beta stage sooner :P Now back to the issue... I had error like that when SVN messed up Profile file merge and I got 2 times an entry about same field. Never heard about it having anything to do with Histories, good to know. –  eyescream Jan 9 '13 at 19:46
    
I have to wait 19 hours before I can accept my own answer (grrrr). On the issue, this can also happen if a RecordType that exists in both orgs has the label (but not the api name) changed in the source org. –  DaveS Jan 9 '13 at 23:28
    
Still getting this bug. Did anyone log a case? –  Jeremy Ross May 1 at 17:47
add comment

Another possibility, for others that may encounter that error message, is listed on the DreamFactory Wiki:

Description: Found when you push Record Types and another Record Type with the same API name but different Label exists on the destination.

Workaround: Execute a Compare Asset and ensure that the Labels and API names match on both sides.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.