- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2021 12:21 AM
I am using a dev instance dev64918.service-now.com to load some system configuration data from xml file into cmdb using import set. After loading, I can see the import set table was updated with records properly. However when I tried to use transform map(field map) to transform those data into target table(user defined). I can see the record in import set table was changed into Processed state. However the target table was still empty. Screen shot for the import set table and transform record attached. Anyone can help on this?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2021 11:13 PM
Hi,
If your query is resolved, please mark the answer as correct and close this thread for others.
Regards,
Shloke
Regards,
Shloke

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2021 12:49 AM
In the transform map, are all mandatory field mapped to a value? Seems like there's a mistake in the transform map. Try hardcoding the values and checking if a record is entered. If it is, try outputting field values to a log to make sure they are correct.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2021 01:17 AM
Hi,
Just attached the definition of transform map & the target table cmdb_ci_zos_server inheritance hierarchy as screenshots below. For the transform map, I am just using Auto Map Matching Fields to create field maps. No idea about what are all mandatory fields here. You referred there is a mistake in the transform map. Could you please point out?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2021 05:50 PM
Just find that the field maps are the cause. Seemed I defined maps from a source table field, which is just storing a blank. When switching to a proper field, the target table got populated properly.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2021 10:11 PM
Good to hear that you've been able to fix the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2021 10:53 PM