Hierarchic Asset Location Mapping
Hi all,
So in v9 of the K1000 we have some very fancy hierarchical location mapping that's possible. We've recently taken a hardware audit so are updating all of our locations in keeping with the new Hierarchical format available, but I'm trying to work out how this can be mapped through the CSV imports Kace can do (before I import all the audited data back in and create a bunch of erroneous fields).
Obviously something like Building A->Main Office->Desk 4 is different to Building B-> Main Office ->Desk 4, but how do I make K1000 understand this through a CSV import? Are these colonated fields like the Ticket Types on the Service Desk (i.e. "Software::Microsoft Office").
Thanks!
Answers (2)
You are not able to "import" the hierarchy when you import assets, you have to remember that the hierarchy is just "smoke and mirrors" and the location table is just a flat table, which is then interpreted by the UI. SO having identically named sub-locations under different main locations may get confusing ;o)
It's a parent, child relationship. Top level locations have a parent of 0, so a room's parent will be the ID of the building, etc. That means you will need the Asset IDs for the import, but I don't know if an import will allow you to set the parent.
