Azure Service Graph Connector - Error in SQL Imports

[ColtinR]

Greetings Community!

I am facing a challenge with the SQL imports. I keep getting the following error when trying to import our SQL databases:

Transformation failed:

java.lang.IllegalArgumentException: Undefined field family
at com.snc.cobject.ComplexObject.setRawValue(ComplexObject.java:253)
at com.snc.cobject.ComplexObject.setValue(ComplexObject.java:328)
at com.snc.cobject.ComplexObject.setValue(ComplexObject.java:343)
at com.snc.cobject.ComplexObject.setValue(ComplexObject.java:343)
at com.snc.cobject.ComplexObject.setRawValue(ComplexObject.java:245)
at com.snc.cobject.ComplexObject.setRawValue(ComplexObject.java:236)
at com.glide.transform.transformer.OutputMapper.map(OutputMapper.java:57)
at com.glide.transform.transformer.Transformer.transform(Transformer.java:587)
at com.glide.transform.transformer.Transformer.transformBatchWithWildCardRules(Transformer.java:742)
at com.glide.transform.transformer.Transformer.transformInBatch(Transformer.java:641)
at com.glide.robust_transform_engine.TransformerWrapper.transform(TransformerWrapper.java:53)
at com.glide.robust_transform_engine.RobustTransformEngine.transformRteInputs(RobustTransformEngine.java:309)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.sendToRobustTransformEngine(RobustImportSetProcessor.java:137)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.processBatch(RobustImportSetProcessor.java:118)
at com.glide.db.impex.transformer.service.RobustImportSetProcessor.transform(RobustImportSetProcessor.java:84)
at com.glide.system_import_set.ImportSetTransformerImpl.doRobustImportSetTransform(ImportSetTransformerImpl.java:166)
at com.glide.system_import_set.ImportSetTransformerImpl.transformAllMaps(ImportSetTransformerImpl.java:114)
at com.glide.system_import_set.ImportSetTransformer.transformAllMaps(ImportSetTransformer.java:91)
at com.snc.automation.ImportSetTransformerJob.runTransform(ImportSetTransformerJob.java:291)
at com.snc.automation.ImportSetTransformerJob.execute(ImportSetTransformerJob.java:103)
at com.glide.schedule.JobExecutor.lambda$executeJob$1(JobExecutor.java:198)
at com.snc.db.data_replicate.replicator.DataReplicationAdvisors.runInOriginatorContext(DataReplicationAdvisors.java:74)
at com.glide.schedule.JobExecutor.lambda$inDataReplicationContext$3(JobExecutor.java:228)
at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:201)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:181)
at com.glide.schedule.JobExecutor.execute(JobExecutor.java:171)
at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:612)
at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$3(SchedulerWorkerThread.java:404)
at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:404)
at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:180)

This started most recently 5 days ago and was working previously.

I did notice the family attribute is empty but it's also not mapping to anything in the RTE's

Any help would be appreciated!

[Tanushree Maiti]

1. Go to sys_dictionary.list to confirm the column name exists on the target table.

2. Double-check that family is spelled correctly in your Select/Where/Order By clause.

3. If the table defines the column as Family/FAMILY, but you queried family, it might throw an error

4. Lastly validate if family field is  in a scoped application and if you are trying to access a field in a different scope without proper cross-scope privileges.

[Laveena-Agarwal]

Hi @ColtinR 

I would recommend not making any changes to the OOB Service Graph Connector. If any modifications have already been made, it’s better to revert them.

The best approach here would be to raise a Hi case with ServiceNow for the Azure SGC issue and share the error details. Since this is an OOB functionality, it is expected to work as designed, and ServiceNow support should be able to help identify the root cause.

I’ve seen a similar situation earlier where an SGC was working fine initially but later failed. In that case, ServiceNow identified that the issue was caused by customization in IRE rules.

If in your case there are no customizations involved, then it’s possible that the issue lies within the product itself, and ServiceNow can help address it.

[ColtinR]

@Laveena-Agarwal / @Tanushree Maiti Thank you, I'm going to check into this and get back. I know the only customization we made was as directed by servicenow, but the errors were prior to this change.

I have raised a support request to servicenow team and they are currently looking into it. From what we have seen, the issue appears to be extra fields that the ETL inserted when opening up the mappings which is something that they said they have seen happen before.

[ColtinR · Accepted solution]

UPDATE: The issue here was that for some unidentified reason, the transform maps when opening the ETL ended up inserting a bunch of duplicate mappings. Removing the additional mappings that were auto created solved the issue.