Resolving match conflicts
What to do with devices in the Needs review queue: link, create, ignore or merge.
When AssetTrove isn't sure which asset a discovered device belongs to, it puts the device in the Needs review queue on the Discovery page. You need permission to resolve conflicts (Asset managers have it).
What you see
For each device, AssetTrove shows up to 10 candidate assets with their score and the reasons behind it, for example:
| Asset | Score | Signals |
|---|---|---|
| LT-0042 | 80 | Hardware UUID +80, Hostname +15, Device management ID +100, Serial conflict −100 |
| LT-0117 | 60 | Serial without manufacturer +60 |
Your options
| Action | Use it when | What happens |
|---|---|---|
| Link | You know which asset it is | The device is linked to that asset and its software moves with it. Tick Update the asset's serial number when the hardware was repaired with a new board; AssetTrove records a component replaced event |
| Create asset | It's a device you didn't have in AssetTrove | A new asset is created from the device's details. You can set the asset tag, category, location and cost centre |
| Ignore | It's out of scope, for example a lab or test machine | The device is kept but its software doesn't count towards licence use. A note is required |
| Merge assets | Two assets turn out to be the same physical device | One asset survives. The other is retired and its history, assignments, licences and identifiers move to the survivor |
Your decision is remembered: a device you linked stays linked and an ignored device stays ignored on later syncs. Each decision is recorded in the audit log.
When merging isn't allowed
AssetTrove refuses to merge two assets if both currently have someone assigned, or if their custody periods overlap. Return one of the devices first, so the history stays consistent.
Still have a question? Email rory@assettrove.eu and we'll get back to you.