Jump to content

Asset Import Utility


Recommended Posts

I've been doing some more testing with the Asset Import Utility and it now seems to be duplicating entries rather than updating the ones that already exist

It wasn't doing this when I first started testing it a few weeks ago, I've now got 3 entries per machine

Has anything changed in Service Manager recently that may have caused this?

I would have thought that it would look at the machine name as being a primary key and not allow duplicates



Link to comment
Share on other sites

Hi Pete,

Nothing should have changed relating to this recently. This is usually down to a configuration issue in the conf.json file. 

The unique identifier (from the DB) needs to be written in the h_name column of both the AssetGenericFieldMapping and AssetTypeFieldMapping objects. Otherwise the tool can’t work out if there are duplicates or not. 

So as a very basic example (taking some extracts from the conf.json file:

"AssetID": "ComputerName"
"Query": "SELECT [ComputerName], [Manufacturer] from DatabasesAssets
"h_name": "[ComputerName]",

If the unique identfier from the DB is not descriptive enough to be useful as the asset name, then you could always concatenate this and another column in the SQL query to create a value to be used as the unique identifier. 

If you still have issues, it may be worth posting the relevant extract from your conf file here (obviously ensuring not to post any sensitive or password/security information). 

Kind Regards


Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...