Unique Key violation detected by database (Duplicate entry 'e7aa93430f6e7a007bd40eece1050ef4' for key 'PRIMARY')
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-10-2017 05:25 AM
Hi ,
Getting "Unique Key violation detected by database" error while creating incident record in Test Instance.
Actually i have moved one updateset from Dev to Test.after that i have tested in Test instance getting above error.
While moving updateset getting some "Collision" as '5' after that only getting error. Please look the error in the attachment.
Please help on this issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-10-2017 06:06 AM
Hi immanuel,
The record sys_id would have already present in your test Instance, that is the reason you are getting this error.
Its never a right practice to transfer record from Update set.
Better use Import/Export feature.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-10-2017 06:07 AM
Hi,
Can you check if you have written an on before business rule on the incident which calls current.update() or any insert action?
Thank You
Please Hit Like, Helpful or Correct depending on the impact of response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-10-2017 06:17 AM
Please check if there is any current.update() statement exists in Business rule written on incident table.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-24-2020 03:17 AM
Thank you, for me it was in a script include called by the BR. But your answer was spot on