The CreatorCon Call for Content is officially open! Get started here.

Commmitting Update set showing error

venkatraman2
Tera Contributor

While importing update set there was scope error missing shown in preview. After accepting current update in the preview, at committing it was showing like,

 

FAILED TRYING TO EXECUTE ON CONNECTION glide.12 (connpid=6611): INSERT INTO sys_metadata (`sys_updated_on`,`sys_class_name`,`sys_id`,`sys_updated_by`,`sys_created_on`,`sys_name`,`sys_scope`,`sys_created_by`,`sys_mod_count`,`sys_package`,`sys_update_name`,`sys_policy`) VALUES('2022-05-16 10:14:09','sp_instance_table','03ce59fc87270110643343fc0ebb35e1','admin','2022-05-16 10:12:31',NULL,'a03b26b387970110643343fc0ebb35e2','admin',3,'f46b61f407230110f964f7108c1ed083','sp_instance_table_03ce59fc87270110643343fc0ebb35e1',NULL),INSERT INTO sp_instance (`short_description`,`css`,`color`,`sp_column`,`title`,`sys_id`,`id`,`class_name`,`sp_widget`,`order`,`widget_parameters`,`active`,`url`,`glyph`,`size`) VALUES(NULL,NULL,'default','5a3e9dbc87270110643343fc0ebb3597',NULL,'03ce59fc87270110643343fc0ebb35e1',NULL,NULL,'34b170b087a30110643343fc0ebb35ac',1,NULL,1,NULL,NULL,'md'),INSERT INTO sp_instance_table (`sp_page`,`sys_id`,`field_list`,`table`,`display_field`,`order_direction`,`filter`,`maximum_entries`,`order_by`) VALUES(NULL,'03ce59fc87270110643343fc0ebb35e1','external_order_id,bpo_id,order_status','x_819341_cg_global_orders',NULL,'asc',NULL,5,NULL)
java.sql.BatchUpdateException: (conn=6611) Duplicate entry '03ce59fc87270110643343fc0ebb35e1' for key 'PRIMARY'
 

 

Below adding the screenshots for reference. How can i resolve this? Thanks in advance

2 REPLIES 2

Musab Rasheed
Tera Sage

Hi,

Mostly it should not create issue, but go throw below link.

https://community.servicenow.com/community?id=community_question&sys_id=d13d2f70db888014f7fca851ca961954

Regards

Please hit like and mark my response as correct if that helps
Regards,
Musab

Hi,

I explored the link but in that the issue was with widget. But here it was showing only sys id. Can't able to find where exactly happens this error.