Bulk update with asset_tag as the unique identifier instead of id #8755

Closed
opened 2025-12-29 20:40:49 +01:00 by adam · 2 comments
Owner

Originally created by @YoucefYousfi on GitHub (Oct 18, 2023).

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

When using the bulk import feature to update, allow users to identify devices with asset_tag, since it's also a unique identifier.

Use case

In our usage of Netbox, we identify devices with their asset_tag, which is common with other applications. Because of that, our users aren't too familiar with the id field, and mainly use asset_tag to identify the devices. This would allow them to easily use the bulk update feature without having to extract the IDs massively before doing a bulk update.

Database changes

No response

External dependencies

No response

Originally created by @YoucefYousfi on GitHub (Oct 18, 2023). ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality When using the bulk import feature to update, allow users to identify devices with asset_tag, since it's also a unique identifier. ### Use case In our usage of Netbox, we identify devices with their asset_tag, which is common with other applications. Because of that, our users aren't too familiar with the id field, and mainly use asset_tag to identify the devices. This would allow them to easily use the bulk update feature without having to extract the IDs massively before doing a bulk update. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:40:50 +01:00
adam closed this issue 2025-12-29 20:40:50 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 17, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jan 17, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Feb 16, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 16, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8755