java.sql.BatchUpdateException: Duplicate Entry...

[Jordan Vignoni]

Good evening,

I'm experiencing an issue where I'm unable to update the Question of a variable in a record producer without getting the following message:

The message is consistent for all record producers, but the information between "question-question_text" and "key 'name_2" changes based on the Question I'm attempting to update.   Also, all the text in the Question column shows as blue (as shown below):

Also, this is only impacting my personal account.   I'm able to impersonate another user with access to edit record producers and updates are able to be made with no issues.   I believe this all started when I tested an onSubmit() client script (that updates the user record when the end-user updates the contact information) using my personal account.   This led me to disable the client script, as well as create another way that documents the contact changes into the record producer (rather than to the user record) because the onSubmit() client script seemed to be the cause in my testing with other accounts.   However, my account still will not allow changes to the Question of an existing variable on any record producer.

Any ideas on how to resolve this message from showing when editing the Question of a record producer?

Thanks in advance!

[bernyalvarado]

Hi Jordan,

Have you tried deleting the variable and then creating it again?

Thanks,

Berny

[Jordan Vignoni]

Hi Berny,

Yes, I have tried to delete the variable and recreate it.   I'm able to recreate it successfully, but it still shows me the same message as when trying to update the Question of an existing variable.   I suppose that could work, but I really do not want to delete and recreate every variable on a record producer that needs editing.

Thankfully, this is only in Development so I can easily recreate my account with the same permissions to permanently get around it, but I wanted to see whether the root cause could be identified

Cheers,

Jordan

[bernyalvarado]

Hi Jordan, from what you explain it appears some entry in some table used internally within ServiceNow for the record producers will have been duplicated. If something like that happens to you in Production you can always open a Hi ticket to receive the appropriate support. The root cause on those type of situations often has to do with a "raise condition" between two system operations on which the system ends on a bad state.

Since you're using you Development instance i'll suggest you don't worry about it.

Thanks,

Berny

[mikemorales]

This post is a bit old and not sure if you ever got resolution on this but wanted to make a comment.  I have noticed this error and other random errors localized to a single account.  What I have found is the culprit is the user record for the account that is impacted.  Basically, the setting set to a blue Null which is not a valid selection.  Once I changed this to the proper setting/valid setting, the account no longer was impacted.  I still need to look into this further to determine why I am getting account settings changed to something that is not valid, but I know to check this first if there is an issue on a single account.

I hope this helps!

Thanks,

mike