- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:29 AM
Hi All,
Whenever I try to create a new Standard Change and select a template, an error message is displayed every time- " Unique Key violation detected by database (Duplicate entry '741ad1404fa37a00445cecd18110c73b' for key 'PRIMARY') "
I have checked Dictionary for all fields in Standard Change Form for Unique checkbox true, but all are false still it displays this error. The sys_id in the error message is different everytime I create new Standard change. How can I get rid of this error.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:34 AM
Hi Arpita
Make sure you don't have current.update in any of the business rules created.
Can you go to the BR table and check script contains current.update() and when is before in the filter conditions.
Cheers
R0b0

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:34 AM
I found something similar related to business rules being fired at the wrong time.
You may find this helpful.
how to remove Unique Key violation detected error in change form once record is submitted
Related to BRs...
Business Rules Best Practices - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:34 AM
Hi Arpita
Make sure you don't have current.update in any of the business rules created.
Can you go to the BR table and check script contains current.update() and when is before in the filter conditions.
Cheers
R0b0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 05:59 AM
Hey thanks for the reply.. It worked..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-09-2019 02:37 AM
Hi Robo,
We are facing same issue in our portal. but we r not using current.update() in business rule but still this issue is coming.
can u help us. why this is happening.