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

Implement Decimal and/or Float as a custom field data type #6975

New Issue
Closed
opened 2025-12-29 19:47:22 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:47:22 +01:00
Owner
Copy Link

Originally created by @eronlloyd on GitHub (Sep 13, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.3.2

Feature type

Change to existing functionality

Proposed functionality

While the Integer custom field data type is usage for many use cases, there are others that require decimal or float precision.

I propose that one or both of these numeric types be added as choices for custom fields to enable such use cases. @jeremystretch pointed out that the underlying JSON serialization would have to be taken into consideration for the different types as JSON doesn't distinguish between numerical types. This constraint may make sticking with Decimal the better option to preserve precision.

Use case

As an example, I'm trying to create custom fields for optical insertion loss (IL) for ports and attenuation for cables, but this needs to be in decimal format to accurately represent the decibel values.

Database changes

Stored as JSON in the DB, so shouldn't affect the data model. Requires changes when serialized/de-serialized into memory.

External dependencies

None

Originally created by @eronlloyd on GitHub (Sep 13, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.3.2 ### Feature type Change to existing functionality ### Proposed functionality While the Integer custom field data type is usage for many use cases, there are others that require decimal or float precision. I propose that one or both of these numeric types be added as choices for custom fields to enable such use cases. @jeremystretch pointed out that the underlying JSON serialization would have to be taken into consideration for the different types as JSON doesn't distinguish between numerical types. This constraint may make sticking with Decimal the better option to preserve precision. ### Use case As an example, I'm trying to create custom fields for optical insertion loss (IL) for ports and attenuation for cables, but this needs to be in decimal format to accurately represent the decibel values. ### Database changes Stored as JSON in the DB, so shouldn't affect the data model. Requires changes when serialized/de-serialized into memory. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:47:22 +01:00
adam closed this issue 2025-12-29 19:47:22 +01:00
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 status: accepted 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#6975
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?