CDW and SNOW Integration

[Corey Harris]

Good afternoon, everyone,

Has anyone integrated CDW with SNOW? 

The context of this question is that anytime my company buys hardware from CDW, a file is generated with serial numbers and asset tags (along with other details) of all of the items being shipped to us. Per CDW's documentation, at least from what I found, we're using an API to post the data from CDW into a custom table that I built out. On that end, everything is working fine. Every item that we buy from CDW, it is posted to the custom table with all of the information of that item. My ultimate goal is that when something is inserted into the custom table and it has an asset tag, it will automatically create the asset on the hardware asset table and remove the manual process of creating the asset.

Is this possible? If so, could someone give me a little guidance or best practices on how to accomplish this?

I have attached the documentation from CDW of all the information that CDW posts to the custom table but I want to move anything with an asset tag from the custom table to the hardware assets table.

Best regards,

Corey

[Tony Chatfield1]

Hi, based on your details and description it seems like you need your 'custom' table to be a temporary import table IE a table extended from 'Import Set Row', the REST API can then push in new records and you can use OOB transform functions to coalesce and process your records and insert new or update matched asset as required.

Import sets (servicenow.com)

[Corey Harris]

Thanks Tony!

Well interesting situation, my company wants everything that we purchase to be written to the custom table for audit purposes. I'm using an import set to write the purchased items from CDW over to the custom table currently. But now my organization wants anything with an asset tag (computers) to be moved over to the hardware asset table. I'm thinking of using a business rule to accomplish this but I'm not sure if there is a better way to accomplish this or not?

[SteveMac1 · Accepted solution]

Corey you could just create another transform and run them both on the original import table. That way you have all the functionality of import sets / transforms and don't have out all the logic in a business rule. 

If you need to 'filter' the records, you can have those checked in the onBefore or onStart script (whichever runs for each record; I can't remember which one it is).

[Corey Harris]

Thanks SteveMac1! That was an option I didn't think about but that would definitely be easier than trying to write the logic in a business rule.

Best regards,

Corey