API Service Graph connector for Apigee X - v2.2 to v2.3 upgrade impact<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Summary of changes In API Service Graph Connector for Apigee X v2.3, we have updated the Source Native Key (SNK) value for the API Frontend CI class. Impact If the integration was previously run in v2.2 and populated the API Frontend (cmdb_ci_api_frontend) table, then after upgrading to v2.3 and running the integration again:In the Source (sys_object_source) table, a single API Frontend may be linked to multiple SNK values due to the update in the SNK for the API Frontend CI class.Some API Frontend records may be marked 'Non-Operational', even though they are active on the Apigee X platform. Why this happens After data ingestion, the connector executes a scheduled post-import script.This script identifies the records that were not imported in the last pull using the Source (sys_object_source) table and marks them as 'Non-Operational'. Since, API Frontend records are now linked to multiple SNKs after the SNK change as part of the version upgrade, recently imported API Frontend records may also get marked 'Non-Operational'. ResolutionDue to restrictions on deleting records from CMDB tables, we are unable to furnish a fix script to delete records from the CMDB CI API Frontend table following the upgrade to v2.3. The CMDB table does not permit record deletion from a different application scope. Follow these steps to resolve the issue: 1. Manually run the following script in the 'Script - Background' (https://instancename.service-now.com/sys.scripts.do) within the CMDB CI Class Models (sn_cmdb_ci_class) application scope to permanently delete only SGA-Apigee X discovery scope records from the API Frontend table. This process might take some time as it also removes related records from the sys_object_source table var apiFrontendGr = new GlideRecord("cmdb_ci_api_frontend");apiFrontendGr.addQuery("discovery_source", "SGA-Apigee X");apiFrontendGr.query();apiFrontendGr.deleteMultiple(); 2. Re-run the integration by executing the parent scheduler. This will repopulate all API Frontend data correctly without any SNK issues. NOTE: If the application scope sn_cmdb_ci_class is not available for selection in the Scripts background, it can be run by creating a Fix script (sys_script_fix) under the CMDB CI Class Models (sn_cmdb_ci_class) scope.