IntegrationHub - Import via script - How to update inserted record?

[GB14]

Hello,

We created an ETL to import WYSE Devices from the Dell portal to SN. 

The first import and insert worked fine, We were able to import all 1000 devices into SN without any issues. Now we have upgraded these devices to a different/latest model but the CI model is not updating.
I checked the import set and confirmed the devices in it have the SN but for some reason, our CI's are not getting updated. Any suggestions if we have to add Reconciliation rules for the import set or is there something else is needed to update the model in SN?

Thanks in Advance,
G

[Kim Rasmussen · Accepted solution]

I am unsure if you are using the "old" transform or IntegrationHub ETL (IH ETL) ?

The right way in this case would be using the IH ETL, this ensures that all import data goes through the Identification and reconciliation Engine (IRE) and Multisource if you have that enabled. The IH ETL uses what is called Robust Transforms but is similar to the "old" transforms.. 

[GB14]

Hello @Kim Rasmussen 

we are using IH ETL. 

Does this mean I have to add Reconciliation Rules here for the import set?

Thanks 

[Kim Rasmussen]

I would guess you need to look at the Identification Rules. But it of course depends on what the problem. Do you get duplicates? then it is identification, if you just do not get any update of the attributes then you most likely need to revisit the Reconciliation rules.

Do you get data from SCCM or ServiceNow on the same CIs as well? If not then the 2 rules you have should not affect your discovery source, but if the data has been updated by any of the other sources there could be rules that retain that date over you WYSE data.

[GB14]

Thanks @Kim Rasmussen 
We are getting the WYSE Data from an API call to SN. No duplicates, just not getting the new updates when the device is updated to a different model. We are not getting the WYSE Data from SCCM or SN, I will try to test in Dev by adding the new reconciliation rule for the import set. 

I will share the updates on this laster this week. Thanks again for your reply. 🙂