
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2020 11:05 AM
I am looking at export sets and I am trying to understand the best way to export the CMDB using XML. I know that I can go into each class table and create a set to export, but I would like to know if I can export a table that will drop ALL CI's into one XML. I tried to create an export set at the Configuration Item table CMDB_CI, but the XML was only 96KB. Is there a way to do this to reduce the number of sets, and imports required?
Solved! Go to Solution.
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-30-2020 01:49 PM
Hi - beware that depending on what starting class you export from at top of hierarchy... like cmdb_ci... will probably limit the attribute/fields that are exported to XML. Since classes deeper in CMDB hierarchy add attributes, (i.e. windows servers), fields will probably be missing from the export. Maybe this doesn't matter for your use case - but be informed. An export from the root of the CMDB could provide base CI info and sysid, fundamental stuff, etc. but unlikely to provide details defined (added attributes) per class table. i could be wrong - I haven't tried this - but I'd be sure to check your export results.
If a true, complete copy of every CI is required something beyond a simple XML export may be needed.
Hope this helps?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2020 11:32 AM
I tested and confirmed that you can in deed drill down as an option, but that report does not output usable data. The best way is indeed to export each class to ensure that all the data wanted is in deed collected. Else you will losse data in each class. I hope this helps.