Robust Import Set Transformer

Shalani Rajendr
Tera Contributor

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!

 

1 ACCEPTED SOLUTION

Hi @Shalani Rajendr 

There is Conditional script existing for Software Install table

SwathiPedireddy_0-1743482798201.png

Open the Entity and modify the script as below and the processing time may increase because of checking the status of computer before inserting

SwathiPedireddy_1-1743482861117.png

 

Thanks,

Swathi

View solution in original post

21 REPLIES 21

Kieran Anson
Kilo Patron

Can the business advise on why they've created such a business rule? Is it needed or can it be deleted ? 

Hello @Kieran Anson ,

    It's a requirement where during the import if the installed_on.operational_status == 'ceased' or 'under_construction' then insertion shouldn't happen.

But why? You're going to potential end up with reconciliation issues. Has the impact been explained to the customer? 

 

As it's affecting the performance complete analysis is done on how to resolve the issue. Is there any alternative solution to business rule where skipping of records are done without triggering logs. As per my  analysis to add before script in data source in order to skip the records.

As there is limited documentation I'm not sure about the output.