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

"Invalid value for custom field: Value must be a string" when bulk updating #7898

New Issue
Closed
opened 2025-12-29 20:29:40 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:29:40 +01:00
Owner
Copy Link

Originally created by @domainzero on GitHub (Apr 12, 2023).

NetBox version

v3.4.4

Python version

3.9

Steps to Reproduce

  1. Create a device custom field with type Integer and any name.
  2. Create two or more devices, filling in the new custom field with any integer.
  3. Change the custom field created in step one to type Text.
  4. Select the devices that were just created and edit, changing anything but the custom field.

Expected Behavior

All items bulk update successfully.

Observed Behavior

I receive the following error: Invalid value for custom field 'field': Value must be a string. This error does not occur if I edit a device individually.

Originally created by @domainzero on GitHub (Apr 12, 2023). ### NetBox version v3.4.4 ### Python version 3.9 ### Steps to Reproduce 1. Create a device custom field with type `Integer` and any name. 2. Create two or more devices, filling in the new custom field with any integer. 3. Change the custom field created in step one to type `Text`. 4. Select the devices that were just created and edit, changing anything but the custom field. ### Expected Behavior All items bulk update successfully. ### Observed Behavior I receive the following error: `Invalid value for custom field 'field': Value must be a string`. This error does not occur if I edit a device individually.
adam added the type: bug label 2025-12-29 20:29:40 +01:00
adam closed this issue 2025-12-29 20:29:40 +01:00
adam commented 2025-12-29 20:29:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 12, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Apr 12, 2023): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:29:41 +01:00
Author
Owner
Copy Link

@domainzero commented on GitHub (Apr 12, 2023):

Thanks Jeremy. I have updated the initial bug report.

@domainzero commented on GitHub (Apr 12, 2023): Thanks Jeremy. I have updated the initial bug report.
adam commented 2025-12-29 20:29:41 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Apr 19, 2023):

@domainzero this was fixed with "#11431 - Disallow changing custom field type after creation" in NetBox v3.4.8. Changing the type of the custom field is not allowed after creation.

@arthanson commented on GitHub (Apr 19, 2023): @domainzero this was fixed with "[#11431](https://github.com/netbox-community/netbox/issues/11431) - Disallow changing custom field type after creation" in NetBox v3.4.8. Changing the type of the custom field is not allowed after creation.
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 type: bug
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#7898
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?