starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Auto-increment CustomField #6941

New Issue
Closed
opened 2025-12-29 19:47:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:47:02 +01:00
Owner
Copy Link

Originally created by @PieterL75 on GitHub (Sep 7, 2022).

NetBox version

v3.3.2

Feature type

New functionality

Proposed functionality

Create a custom field that auto-increments when a new object is created.
The custom field would hold a 'template', as in some cases a prefix is needed
Ex: DEV000000, DEV0000ALL, 000000SW where the 000000's would increment

Use case

Device in the racks are only labeled with global a unique number. (we don't use devicenames for compliance and shortlabels)
An auto-incrementing custom field would give us the abiility to create unique numbers for each created device

Database changes

No response

External dependencies

No response

Originally created by @PieterL75 on GitHub (Sep 7, 2022). ### NetBox version v3.3.2 ### Feature type New functionality ### Proposed functionality Create a custom field that auto-increments when a new object is created. The custom field would hold a 'template', as in some cases a prefix is needed Ex: DEV000000, DEV0000ALL, 000000SW where the 000000's would increment ### Use case Device in the racks are only labeled with global a unique number. (we don't use devicenames for compliance and shortlabels) An auto-incrementing custom field would give us the abiility to create unique numbers for each created device ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:47:02 +01:00
adam closed this issue 2025-12-29 19:47:02 +01:00
adam commented 2025-12-29 19:47:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 7, 2022):

While I can appreciate the use case, I'm afraid this is just too much logic to pack into a custom field, which are intended to store static, prescribed values. What you're describing is akin to a database sequence, but actually more complex because you've employed a template to render the iterative portion of the value.

Instead, I'd suggest writing a simple plugin to hook into Django's post_save signal and employ whatever logic you'd like to automatically set these values. This approach is going to be much more flexible, as it allows for the consideration of other device parameters, such as role and status, when determining the value to apply.

@jeremystretch commented on GitHub (Sep 7, 2022): While I can appreciate the use case, I'm afraid this is just too much logic to pack into a custom field, which are intended to store static, prescribed values. What you're describing is akin to a database sequence, but actually more complex because you've employed a template to render the iterative portion of the value. Instead, I'd suggest writing a simple plugin to hook into Django's [post_save](https://docs.djangoproject.com/en/4.1/ref/signals/#django.db.models.signals.post_save) signal and employ whatever logic you'd like to automatically set these values. This approach is going to be _much_ more flexible, as it allows for the consideration of other device parameters, such as role and status, when determining the value to apply.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6941
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?