device module profile type - properties jsonschema - convert enum options to dropdown list in forms #116

New Issue

MrUnknownDE · 2026-04-05T16:21:50+02:00

MrUnknownDE commented

2026-04-05 16:21:50 +02:00

Originally created by @ITJamie on 3/18/2026

NetBox version

v4.5.5

Feature type

Data model extension

Proposed functionality

create a module profile with the following jsonschema

{
    "properties": {
        "form_factor": {
            "enum": [
                "onboard",
                "mezzanine",
                "pcie",
                "ocp",
                "lom",
                "unknown"
            ],
            "title": "Form factor",
            "type": "string"
        },
        "max_speed_gbps": {
            "title": "Max port speed (Gbps)",
            "type": "number"
        },
        "media": {
            "items": {
                "enum": [
                    "copper",
                    "sfp",
                    "sfp28",
                    "qsfp",
                    "qsfp28",
                    "base-t",
                    "dac",
                    "aoc",
                    "unknown"
                ],
                "type": "string"
            },
            "title": "Media",
            "type": "array"
        },
        "port_count": {
            "title": "Port count",
            "type": "integer"
        }
    },
    "required": [
        "port_count"
    ]
}

2: create a module type and assign it to that profile created above
The "media" field appears once the module type is selected.
note that the field is a text field & that it does not give any hint about allowed values (possibly another fr?)

instead of this being a text array field that is csv formatted (note that it will accept sfp,sfp28 )

if this was instead changed to be a dropdown multiselect box when its type:array + enum list it would be much more user friendly

Use case

right now the fields which use a predefined list of values, its not currently obvious as to what values are accepted until the form validation is done when saving. exposing that list via a hint OR converting it to a dropdown selection (or multiselection box) would be useful

Database changes

n/a

External dependencies

n/a

*Originally created by @ITJamie on 3/18/2026* ### NetBox version v4.5.5 ### Feature type Data model extension ### Proposed functionality create a module profile with the following jsonschema ``` { "properties": { "form_factor": { "enum": [ "onboard", "mezzanine", "pcie", "ocp", "lom", "unknown" ], "title": "Form factor", "type": "string" }, "max_speed_gbps": { "title": "Max port speed (Gbps)", "type": "number" }, "media": { "items": { "enum": [ "copper", "sfp", "sfp28", "qsfp", "qsfp28", "base-t", "dac", "aoc", "unknown" ], "type": "string" }, "title": "Media", "type": "array" }, "port_count": { "title": "Port count", "type": "integer" } }, "required": [ "port_count" ] } ``` 2: create a module type and assign it to that profile created above The "media" field appears once the module type is selected. note that the field is a text field & that it does not give any hint about allowed values (possibly another fr?) instead of this being a text array field that is csv formatted (note that it will accept `sfp,sfp28` ) if this was instead changed to be a dropdown multiselect box when its type:array + enum list it would be much more user friendly ### Use case right now the fields which use a predefined list of values, its not currently obvious as to what values are accepted until the form validation is done when saving. exposing that list via a hint OR converting it to a dropdown selection (or multiselection box) would be useful ### Database changes n/a ### External dependencies n/a

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

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

No Label complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#116