Unique Identifier in CSD 2.0 flow executions. - Support and Troubleshooting

Unique Identifier in CSD 2.0 flow executions. Issue 1. When the CSD 2.0 flows are being executed we could see the flow is being errored out with below error:

FAILED TRYING TO EXECUTE ON CONNECTION glide.14 (connpid=1798135): INSERT INTO sn_ms_intune_spoke_deployment (`mode`,`server`,`sys_id`,`sys_updated_by`,`application`,`sys_created_on`,`sys_mod_count`,`sys_updated_on`,`id`,`intent`,`sys_created_by`,`group`) VALUES('include','b5256e3b1b5146105cb0a792b24bcb80','18f9412e1bed4a5063ddb886d34bcb79','admin','12dbcb4c1be1c61009c58449d34bcbe2','2024-04-16 17:49:44',0,'2024-04-16 17:49:44','8f7655ba-b14e-4f40-a6eb-e16715c15c2d_0_0','available','admin','7cb45b0c1b25c61009c58449d34bcbdf') /* colttest2015, gs:glide.scheduler.worker.1, tx:0239b8e21bad4a5063ddb886d34bcbea */ Unique Key violation detected by database ((conn=1798135) Duplicate entry '8f7655ba-b14e-4f40-a6eb-e16715c15c2d_0_0' for key 'id') : java.sql.SQLIntegrityConstraintViolationException: (conn=1798135) Duplicate entry '8f7655ba-b14e-4f40-a6eb-e16715c15c2d_0_0' for key 'id':

2. Screenshot as below for reference.

Cause This is because there is Unique check box checked on the ID field which in turn is not allowing the records with same ID to get inserted into ServiceNow.

If we see from the below screenshot the Unique is true for ID:

Resolution -- You can use the workaround with unchecking uniqueness on the db field.

-- But this may not be updated from the UI. If the first step is being failed, need to follow below procedure.

1. Make sure the plugin is installed: com.snc.planned_task_v2

2. We have to create below records in sys_scope_previlige table

First Record:

i.source Scope - Microsoft Intune Spoke ii.Target scope - Global iii.Target Name - sys_dictionary iv. Target Type - Table v. Operation - Read vi. Status - Allowed vii. Application - Microsoft Intune Spoke

Second Record: i.source Scope - Microsoft Intune Spoke ii.Target scope - Global iii.Target Name - PTGlobalAPI iv. Target Type - Script Include v. Operation - Execute API vi. Status - Allowed vii. Application - Microsoft Intune Spoke

3. We have to take XML backup of the BR: Redirect Unique Index Change, inactivate the BR.

4. Need to Execute below Background script as the records may not be updated manually from the UI.

**Script: var profileAssociationGr = new GlideRecord('sys_dictionary'); profileAssociationGr.addQuery('name', 'sn_ms_intune_spoke_deployment'); profileAssociationGr.addQuery('element', 'id'); profileAssociationGr.query(); if (profileAssociationGr.next()) { new global.PTGlobalAPI().updateMultipleDictionary(profileAssociationGr, { unique: false }); } **

5. Once the above Script is executed we could see that the unique attributes are unchecked. Then we need to activate the BR which we inactivated in step 3.