Summary - I have a ;list of 8000 computer's asset tags and their corresponding "main user" in an SQL database belonging to our "snow inventory system"
I want to import them into Landesk and map them to Configuration management\configuration Item\Snow Freq User (a str attrib i created)
but when I do I get 8000 errors along the lines of:
29/01/2018 15:13:32 : There was an Object Type Missmatch. Config._Laptop != Config.ConfigItem (076969)
I think this is because we have "sub-objects" like Configuration item\baseunit ( or laptop etc) with collection(?) linking and sharing some of the attribs
I dont see why I shouldnt be able to match on CI number and put a string into the "frequent user" attrib as both of these are at the top level (configuration item) and leave the ones that are not matched blank.
I have a feeling we tried this a couple of years ago and then decided we needed to put 2 separate imports against laptop and baseunit - but this resulted in thousands of extra records being created when the target laptop was a baseunit , or vice versa.
Which brings me onto question 2
Sometimes we like an import to create a new record in Landesk if there is no match - for instance if a newuser has been created in AD.
And sometimes We'd like it to forget it if theres no match and move on - like in the above laptop/baseunit example.
How do you tell an import which of those to do?