Asset Table issues

[Jim]

Hi, hopefully I can explain this as well as it is in my mind  

 

We have an issue with the way the users have resolved in the used by or owned by fields, We use a nightly script to update the used by, and owned by we uploaded a csv using the same asset import tool which will be updated manually when we allocate assets. when doing it manually it does resolve correctly. The correct way is the bottom one 

 

For some reason they display differently as pictured below, however there is no difference in these for the scripts? it affects when using the filter within asset management to return devices either used by or owned by the user 

 

 

 

[Steve Giller]

What script are you using, and what import tool (if a Hornbill one, which version) uploads the CSV?

[Jim]

Not sure on the version, its pre v4 though definitely, and the goDBAssetImport for both sccm and csv uploads

[Steve Giller]

The first step would have to be to upgrade to the latest version (currently v4.1.1)

There is little value in troubleshooting an issue that may be fixed already.

You will need to review the documentation as there have been changes to the Authentication mechanism, and pay particular attention to the First Run section as failure to do so will almost certainly prevent the Tool from running to a schedule.

[Jim]

Hi Steve, This is something I have looked at however we have multiple users that may log on to run these when there are issues pending availability of engineers, thus making the way this encrypts a key very hard for us to work with, we also do not create generic accounts on servers which is why we have not updated 

[Steve Giller]

I believe (although it's not my area of expertise) that you should be able to save the executable under an individual Windows User's profile - this would mean that the executable and its configuration would be isolated to that account, including the encrypted authentication information.

That should mean that whichever engineer logs on the executable is run under the same User that set it up.

Alternatively, if this is a manual process every time, you can, as detailed in the documentation, just delete the import.cfg file from the folder where the import binary resides, and re-run your import from the command line inputting the Instance ID and new API Key as you would have on its first run.

[Jim]

@Steve Giller

This also happens when using the update assets node 'owned by' in hornbill its self so I don't think this is strictly just the scripts with this issue, 

see the below, 

from node update 

 

from asset field its self update

 

the node is like the below with the owned by being the users ID value

- 

 

[Jim]

any chance of this being looked into?