Robust Import Set Transformer

[Shalani Rajendr]

Hello everyone,

      I have a requirement where we have configured service graph connector for Microsoft SCCM to pull data into ServiceNow instance. They have used Robust Import set Transformer where transformer definition type is cmdb integration studio application data source is created and cmdb integration studio entities, entity mapping,entity field mapping, entity engine operation is configured. A scheduled job is created to run this robust import set transformer where transform mapping is done for multiple tables and one of the table is cmdb_sam_sw_install. They have written a business rule on insertion to cmdb_sam_sw_install with condition installed_on.operational_status is one of ceased,under construction then it should abort action(checkbox) is checked.

Due to this everytime during the import thousands of errors are logged. I need to avoid this error in syslog table as it affects the performance of the instance.

Kindly request to suggest a best solution to remove logs from sys log table. Either an alternative solution for business rule or onbefore script in robust import set transformer where the record insertion will be skipped without any error logs in syslog table. As there is no documentation for cmdb integration studio application definition please provide me assistance in resolving this issue.

Thanks in advance!

[Kieran Anson]

Hi,

I was wanting to understand why your customer is wanting to prevent the insertion of certain records. I understand why you're investigating this issue because of the performance impact. But preventing insertion of software related information, particular SAM Pro, seems risky. And I'm wondering if that original BR requirement wasn't fully considered.

[Shalani Rajendr]

Hello,

So from your end your asking to disable business rule and ignore this requirement as it's risky incase of sccm.

[Shivalika]

Hello @Shalani Rajendr 

Instead of using Business rule to prevent insertion handle it in the staging table itself. 

Here in the RTE mapping of the script there is a condition field via which you can add your conditions. 

Second way is, write a Post Import Script to your scheduled import, then it will immediately take action just after import and data won't be going to target table. 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

[Shalani Rajendr]

Hello @Shivalika ,

    Thank you for your response.

    So how to write script in entity mapping?

Main goal is to remove logs errors even it's aborting the insertion of records.

[Shivalika]

Hello @Shalani Rajendr 

The log errors are because you are aborting the insertion ? What's the main reason ? - if logs are because of insertion then handle it in staging table. If not find some pattern and initiate deletion of those logs every day or every few days. 

These are the script options you have in ETL 

You may utilise this if this works or post import script is always an option if you want to use GLIDE API script 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY