custom fields in device types are not inherited #10887

New Issue

adam · 2025-12-29T21:37:16+01:00

adam commented

2025-12-29 21:37:16 +01:00

Originally created by @the-seppel on GitHub (Mar 13, 2025).

NetBox version

v4.2.5

Feature type

Data model extension

Proposed functionality

the custom field should be filled with inherited data.

Use case

create a custom field for a device type
create a new device type with data inside the custom field (e.g. a product number)
create a device from the device type
there is no data inside the custom field of the new device

Expected Behavior

pre-defined fields with data in a template should be inherited for devices.
e.g. a product number.

Observed Behavior

the custom field is empty.

Database changes

.

External dependencies

.

Originally created by @the-seppel on GitHub (Mar 13, 2025). ### NetBox version v4.2.5 ### Feature type Data model extension ### Proposed functionality the custom field should be filled with inherited data. ### Use case create a custom field for a device type create a new device type with data inside the custom field (e.g. a product number) create a device from the device type there is no data inside the custom field of the new device Expected Behavior pre-defined fields with data in a template should be inherited for devices. e.g. a product number. Observed Behavior the custom field is empty. ### Database changes . ### External dependencies .

adam added the type: feature label 2025-12-29 21:37:16 +01:00

adam closed this issue

2025-12-29 21:37:17 +01:00

adam commented

2025-12-29 21:37:17 +01:00

@jeremystretch commented on GitHub (Mar 13, 2025):

It wouldn't make sense to replicate custom field values from a device type to its devices. This would only result in redundant data. Custom fields are intended for storing data unique to a specific object. Attributes which apply to all devices of a type should be defined only on the device type.

@jeremystretch commented on GitHub (Mar 13, 2025): It wouldn't make sense to replicate custom field values from a device type to its devices. This would only result in redundant data. Custom fields are intended for storing data unique to a specific object. Attributes which apply to all devices of a type should be defined only on the device type.

adam commented

2025-12-29 21:37:18 +01:00

@the-seppel commented on GitHub (Mar 13, 2025):

It wouldn't make sense to replicate custom field values from a device type to its devices. This would only result in redundant data. Custom fields are intended for storing data unique to a specific object. Attributes which apply to all devices of a type should be defined only on the device type.

Yes, that's clear. But I don't want to create shared custom fields twice. I only want to show this custom fields in the view of a device. There is no need to create new data. Just the view of the device should contain all information from the parent. (device type)

@the-seppel commented on GitHub (Mar 13, 2025): > It wouldn't make sense to replicate custom field values from a device type to its devices. This would only result in redundant data. Custom fields are intended for storing data unique to a specific object. Attributes which apply to all devices of a type should be defined only on the device type. Yes, that's clear. But I don't want to create shared custom fields twice. I only want to show this custom fields in the view of a device. There is no need to create new data. Just the view of the device should contain all information from the parent. (device type)

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#10887