You need to sign in to do that
Don't have an account?

Windows style error messages..... unknown error in unknown
Hey Guys,
This one has just popped up on a clients org when running test classes, im frantically searching through the config to make sure no one has change something to unique but i havent found anything yet, any ideas?
System.DmlException: Insert failed. First exception on row 0; first error: DUPLICATE_VALUE, duplicate value found: <unknown> duplicates value on record with id: <unknown>
Here is the response from support:
All Answers
I am having the same problem, just starting this afternoon. Every test gives this error when trying to create a test record.
Help!
I too I am experiencing the same problem.
Previously working TestCases are now broken by this error
Hi
Did you manage to solve this error? I am getting in when trying to insert a lead in a test method
Yup, same here, on CS2 and NA3.
Please see response from support:
Thank you for your inquiry. This error is the result of a bug that incorrectly uses an autonumber field. While we do not provide guaranteed timelines for bug fixes, this is expected to be fixed within the coming week. In the meantime, avoid using the DML insert statement in test methods. One workaround would be to query data and perform an update. Test methods do not commit data, so the update will not actually affect the queried data.
We apologize for this regression. If this is critical (you need a fix in minutes, not hours), please log a case with support asking them to link it to bug 230025. We can manually provision an org perm to workaround the issue. We are working on a systemic fix for all orgs right now.
Here is the response from support:
I'm still seeing this on CS2.
After creating a Campaign via the API and I'm getting the:
duplicate value found: <unknown> duplicates value on record with id: <unknown>
When trying to create a CampaignMemberStatus for that Campaign.
Any ideas?
Thanks,
-John
If you've recently refreshed your sandbox after having them apply the patch metioned above, my guess is you will have to have them reapply the patch to your new copy of the sandbox. I noticed that I ran into the same problem right after refreshing our sandbox. I haven't called support to have them reapply the patch but I suspect that is the problem.