Oops! Thanks for catching that Mehmood! I’ve updated the post to give credit where it’s due!

You have wrongly mentioned above that link “https://community.servicenow.com/community/develop/blog/2016/09/21/consumerize-data-imports-to-non-servicenow-administators” is created by Chuck.

It is posted by Michael Ritchie

Thanks,
Mehmood

Hi Sean, The solution we documented here assumes that you have previously created both the import set and the transform map, ideally by manually creating a data source record with an attached file. This solution is intended to address follow-on data imports. It’s not designed to initially create an import set or transform map.

I think I got it. I referenced Table (sys_db_object) with a reference qualifier on the Extends Table to Import Set Row.

Hi Arun,

We elected not to provide an update set for this. The use case for our client was very specific, and we believe that each user of this solution will have requirements that are distinct enough to make a generic update set impractical. You can copy the scripts from the article and paste them into the various records in your instance, then make modifications as needed.

That’s fantastic Brent, thanks for letting us know!

Thanks Jim, your code worked perfectly! My CMDB team are ecstatic with the ease of the new load. It makes their lives a lot easier with the error checking we’ve incorporated and the instant feedback contained in the email. Thanks again for all your efforts that go into making SN|Guru such a valuable resource.