- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 06:12 AM
I have a web service where we are going to populate cmdb_ci_application_software. When creating the web service, I copied all target fields to create custom import set table for source. We need to track the sys_id in the cmdb_ci_application_software. When I'm in the transformation mapping, I see Sys_id in source but do not see sys_id in the Target. Is there a reason why I can't see Sys_ID in target cmdb_ci_application_software mapping?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 01:48 PM
Hi Thomas,
1. You can use the Referenced value field name field on the field map to use the sys_id to map the field there.
Creating New Transform Maps - ServiceNow Wiki
2. I think coalescing on that sys_id value should do it.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 06:15 AM
Hi Thomas,
The sys_id is something ServiceNow creates and assigns to the record and is supposed to be unique in your system. The sys_id of your import table record would need to be different than the sys_id of your application record. Are you generating the sys_id outside of SN and trying to copy it in when creating a record? In that case I would recommend creating another field for something like that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 06:29 AM
I have REST API Explore setup where we query all the records for cmdb_ci_application_software including the sys_id for a 3rd party software application. Applications can change names but once the sys_id is created for application, it never changes in SN. So when we update cmdb_ci_application_software, we can use the sys_id as the coalesce field to update application name.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 06:33 AM
That makes sense. Here are a couple of things that may help:
Importing from Another ServiceNow Instance - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2016 09:10 AM
Thanks for the info Brad. My instance is Geneva. The Importing from Another ServiceNow Instance really helps out a lot.
My import process is Rest Web Service for 3rd party application (source). Data is written to import set with Mode set to Synchronous REST transformation. Records then get updated in SN cmdb_ci_application_software (target). There will be two types of updates
1) Inserts. New applications coming in from 3rd party Web Service will generate new Sys_id in SN (target) for cmdb_ci_application_software. The Sys_id coming in for cmdb_ci_application_software will be blank. They will also pass SN Sys_ids for company and owned_by (reference fields). They know the Sys_ids because they get this from REST API Explorer so they know what's in our system..
2.) Updates. Existing applications coming from 3rd party via Web Service (source) will match on SN (target) Sys_id. So when an update comes from 3rd party they will pass me data but there are a few reference fields that Sys_ids will also be passed. Sys_ID of company and Sys_ID of owned_by.
Question 1: So when I update company and owned_by for cmdb_ci_application_software, how do I just update the Sys_ID for those two reference fields?
Question 2: For Sys_ID in section 5.3 in Importing from Another ServiceNow Instance documentation, when I created New on the Field Map, I was able to select Sys_ID from Target and Sys_ID from Source. Isn't that all that needs to be done?