/build/static/layout/Breadcrumb_cap_w.png

When importing an update to existing asset records

I am trying to import an update to existing asset records I can do it using (e.g. serial number) a primary key how ever the data seems to have quite a few duplicates. Is it possible to use the Asset Unique ID as the primary key (that would fix all my problems)


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Ozhunna 1 week ago
Senior Yellow Belt
0

@kiwiblue. it is basically restricted by the database structure and the GUI overlay. what type of asset records are you referring to? A  lot of customers will assign a unique asset ID to their asstes, often with a site prefix etc and then use that with bar code scanning and as a primary key. 

Posted by: Hobbsy 6 days ago
Red Belt
0

If you have duplicate data then you may have duplicated or orphaned asset records? The Asset import and update, if carried out against the same PK's should only update the single record. If it is updating more than one record then you have an issue with duplicate asset records. Check how your inventory8 links to your assets......

We recommend creating a serial number field in the Device Asset type and then linking Inventory to Asset on that serial field, that way if the asset name, or any other detail changes, the asset will relink.

You will need to go through your asset records to see the Device type assets that are not linked to an inventory record and have a purge. 

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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