Wrong value types on custom fields #4799

Closed
opened 2025-12-29 19:20:44 +01:00 by adam · 0 comments
Owner

Originally created by @exiz01 on GitHub (Apr 20, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.0

Python version

3.6

Steps to Reproduce

  1. Create a custom field for a dcim > device type.
  2. Select a value type as an integer.
  3. Create a new device type through the API and set a string value equal to '1234' for the new custom field in the same request.

Expected Behavior

The new device type should have an integer value on the custom field.
If a device type is created through the GUI this works fine.

Observed Behavior

The new device type has a string value on the custom field

Originally created by @exiz01 on GitHub (Apr 20, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.0 ### Python version 3.6 ### Steps to Reproduce 1. Create a custom field for a dcim > device type. 2. Select a value type as an integer. 3. Create a new device type through the API and set a string value equal to '1234' for the new custom field in the same request. ### Expected Behavior The new device type should have an integer value on the custom field. If a device type is created through the GUI this works fine. ### Observed Behavior The new device type has a string value on the custom field
adam added the type: bugstatus: accepted labels 2025-12-29 19:20:44 +01:00
adam closed this issue 2025-12-29 19:20:44 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4799