Search the Community
Showing results for tags 'import tool'.
Found 3 results
The Asset Import utility v1.9.0 was executed to test the removal of values for a specific field using the '__clear__' as clearcolumn in the SQL statement within the config file but it does seem that the utility inserts a new duplicate record for each asset record instead of updating the existing asset by clearing the value in the existing field.
@Victor In relation to the Organisation Import Tool (1.0.0), there are some fields missing from the example field mapping in the json configuration file. In particular the 'h_notes' field is the one I am after at the moment, but 'h_timezone' and 'h_region' appear also to be missing, but language is present. If I add the missing ones in to the field mapping, will they work or does this require a change to the tool itself? Cheers Martyn
We are importing/updating assets using the asset import tool and SCCM. We use the managedBy attribute in AD to store the asset's assigned owner, and can easily import this into Service Manager. Before I do, my question is; will Service Manager recognise that the CN stored in that field is a user, or will it blindly try and shove the whole CN in there, probably returning a "too long" type error? The Wiki states "h_owned_by":"[UserName]" - when a valid Hornbill User ID (for a Full or Basic User) is passed to this field, the user is verified on your Hornbill instance, and the tool will complete the h_owned_by and h_owned_by_name columns appropriately. however the User ID is the sAMAccountName, not the full CN.