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

Populating custom fields to a specific device type #10727

New Issue
Closed
opened 2025-12-29 21:35:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:35:16 +01:00
Owner
Copy Link

Originally created by @NagaKarthi on GitHub (Feb 4, 2025).

NetBox version

v4.2.2

Feature type

Data model extension

Proposed functionality

Hi Team,

We are using netbox for couple of years. It would be great addition if there is a feature to have custom fields populated specific to device/module types.

ex: I have created a custom field called IMEI that I want to be seen only for module type P-LTEA-EA

With help of Chatgpt got the below response:
You can add logic to check the module type when creating or updating a module and ensure the IMEI number is populated only if the module type is the LTE PIM module (or similar).

Example logic could be:

If module type == "LTE PIM" then IMEI number is required.

I don't want to break the source code as I'm afraid it will make changes on DB Schema and I have to make changes again in netbox source code once netbox new version is released.

Use case

I have created a custom field called IMEI that I want to be seen only for module type P-LTEA-EA

Database changes

No response

External dependencies

No response

Originally created by @NagaKarthi on GitHub (Feb 4, 2025). ### NetBox version v4.2.2 ### Feature type Data model extension ### Proposed functionality Hi Team, We are using netbox for couple of years. It would be great addition if there is a feature to have custom fields populated specific to device/module types. **ex:** I have created a custom field called IMEI that I want to be seen only for module type P-LTEA-EA **With help of Chatgpt got the below response:** You can add logic to check the module type when creating or updating a module and ensure the IMEI number is populated only if the module type is the LTE PIM module (or similar). Example logic could be: If module type == "LTE PIM" then IMEI number is required. --- **I don't want to break the source code as I'm afraid it will make changes on DB Schema and I have to make changes again in netbox source code once netbox new version is released.** ### Use case I have created a custom field called IMEI that I want to be seen only for module type P-LTEA-EA ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 21:35:17 +01:00
adam commented 2025-12-29 21:35:17 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Feb 27, 2025):

Please open a discussion about this subject if you're still having this issue. This may be worth a feature request but it needs further refinement.

@bctiemann commented on GitHub (Feb 27, 2025): Please open a discussion about this subject if you're still having this issue. This may be worth a feature request but it needs further refinement.
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
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#10727
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?