Hi Titus, Do you think you will be able to manage such granularity of CMDB, at physical or logical partition level of a computer HDD?! In this case you should create a configuration item for each partition you mentioned above. Finally, you will relate PC1 c, PC1 e and PC1 d with PC1, a different CI using parent/child relations, for example. I suggest you to keep information about your PC configuration in a single text field (could be CI Description or Baseline #0)instead the creation of many different low level CIs, very hard to manage! If you have an inventory/discovery support application (ZenWorks, SMS, etc) you will have all dynamic information about your current hardware configuration in a different database, and all what you will have to do is to create a link to view those different configuration baselines associated to your PCs. Hope this helps you a little. Regards, Dan
Hi Titus, One field means one value! Except the case when that field is a custom text field (named for example "HDD Size"-text 255 char.) where you can put all mentioned value for the same PC.(PC1, PC2, etc). Create this field using custom fields definition for Configuration Item in your Admin console and import data using a table with only two fields: 1. Search Code - for related PC(as unique key) 2. HDD size - for related text that describes your physical/logical HDD configuration. Is this reasonable? Best regards, Dan
The advisability of this dubious enterprise aside, what is not working for you ? Is your xml file correct? If not, it would help to see your .ini file. Otherwise, it would help to see your import mapping and the import error log.
If I understood correctly what you want: Field = value Search code="PC1" HDD ="c: 130MB,e: 140GB,d: 150MB"
If it is correct you can do this way. 1. create custom field temp_hdd - hidden from users. 2. set import to this field temp_hdd 3. create DB rule that changes HDD field every time when temp_hdd is changed. set HDD= HDD+", "+temp_hdd - concatenate it.
Given you want values from 2 records concatenated together, you might need to get the concatenation happening before importing to Service Desk. We had a similar need and ended up doing a VB script that wrote out the xml in the format that an import could work. We run this script instead of an sd_export then we run sd_import. Dirty but effective.