Duplicate assets occur when two or more records from the same integration refer to the same device and sync into Lifecycle Manager.
| Note: It's expected for the same asset to sync from multiple different integrations. Lifecycle Manager combines this data into one unified asset record. This is not considered a duplicate asset. |
What causes duplicate assets?
Duplicate assets are identified when a single integration contains multiple records for the same device. This can happen when:
- Records share the same serial number or MAC address.
- Records belong to the same client and share the same name, but have no serial or MAC associated with them.
What happens when duplicates are detected
When duplicates are detected from the same integration, Lifecycle Manager merges them into a single asset. Only one instance of the asset appears in your hardware list.
If the records contain any conflicting information, Lifecycle Manager uses the data from the record most recently added to your integrated tool.
We recommend regularly reviewing and cleaning up duplicate records in the source integration to ensure data integrity.
Using Lifecycle Manager to maintain data integrity
Lifecycle Manager highlights duplicate records so you can take action if needed. While duplicate data won't inflate your asset count, it may result in conflicting or inaccurate data in your reports.
As these duplicates are synced from your integrations, Lifecycle Manager can't correct them at the source. However, by bringing them to your attention early, you can resolve issues that could otherwise affect data quality across your systems.
| Any questions? Reach out to our Lifecycle Manager support team by submitting a support ticket. |
Related to