/build/static/layout/Breadcrumb_cap_w.png

Asset Type Customization Question

When I customize the asset type (in this case computer) I have the "Mapped Inventory Field" and "Matching Asset Field"

But how can I use this for more than one field. It doesnt seem to remember the previous association if I change it. And I want it to pull the serial number, user and system description fields. But from what I am experiencing I can only pull one at a time, wait for every system to sync and update that field and then change it to update one of the other field I want to be automatically populated.

 

Am I correct that there really isnt a better way to do this?


0 Comments   [ + ] Show comments

Answers (2)

Posted by: nshah 11 years ago
Red Belt
1

That is correct. What you are talking about is the association between inventory and assets where we link the computer to its asset partner. You want to use something that isnt going to change and not break the association between the inventory entry and asset entry.

 

The options you see are the only ones you get and the rest of the data is either imported into the KBOX via a CSV file or added manually.

 

 


Comments:
  • You could theoretically also create a service desk rule that would copy data from the inventory to the asset module. - chucksteel 11 years ago
  • very true chucksteel. - nshah 11 years ago
Posted by: Timi 11 years ago
7th Degree Black Belt
1

You could export the computer inventory to a csv file (Inventory>Computer>Choose Action>Export to CSV format) and then do an import from the CSV file.  You will need to make sure though that the computer asset type has the necessary fields built into first.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ