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 when bulk edit VM #4404

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

Originally created by @xcdr on GitHub (Dec 23, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.8.6
  • NetBox version: v2.10.2

Steps to Reproduce

  1. add cusom field vm_id to Virtual Machine (Text, required)
  2. add some VM with different vm_id
  3. select VMs on VM list and click "Edit selected"
  4. change "Tenant" and click "Apply"

Expected Behavior

Tenant should be changed as when I edit single VM.

Observed Behavior

Get validation error:
name_of_first_vm_on_the_list failed validation: {'__all__': ["Invalid value for custom field 'vm_id': Required field cannot be empty."]}

Originally created by @xcdr on GitHub (Dec 23, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.8.6 * NetBox version: v2.10.2 ### Steps to Reproduce 1. add cusom field vm_id to Virtual Machine (Text, required) 2. add some VM with different vm_id 3. select VMs on VM list and click "Edit selected" 4. change "Tenant" and click "Apply" ### Expected Behavior Tenant should be changed as when I edit single VM. ### Observed Behavior Get validation error: ```name_of_first_vm_on_the_list failed validation: {'__all__': ["Invalid value for custom field 'vm_id': Required field cannot be empty."]}```
adam added the type: bugstatus: accepted labels 2025-12-29 18:35:40 +01:00
adam closed this issue 2025-12-29 18:35:40 +01:00
adam commented 2025-12-29 18:35:41 +01:00
Author
Owner
Copy Link

@Mothuizyk commented on GitHub (Dec 28, 2020):

I found out it is probably caused by improper bulk edit mechanic. In 2.10.1 as well as 2.10.2 even if editing one field in objects you need to provide values for all of them. Otherwise it defaults to overwriting them to become empty.

As per your example you probably have vm_id marked as required, you didn't provide a value for it because you just want to change "Tenant" so it is empty. Of course requiried field cannot be empty so you get validation error.

@Mothuizyk commented on GitHub (Dec 28, 2020): I found out it is probably caused by improper bulk edit mechanic. In 2.10.1 as well as 2.10.2 even if editing one field in objects you need to provide values for all of them. Otherwise it defaults to overwriting them to become empty. As per your example you probably have vm_id marked as required, you didn't provide a value for it because you just want to change "Tenant" so it is empty. Of course requiried field cannot be empty so you get validation error.
adam commented 2025-12-29 18:35:41 +01:00
Author
Owner
Copy Link

@proudbro commented on GitHub (Dec 28, 2020):

This incorrect behavior affects not only VM's but other models as well such as Racks. It connects with bulk edit custom fields and after I fill required custom fields again it overwrites other custom fields with empty data.

@proudbro commented on GitHub (Dec 28, 2020): This incorrect behavior affects not only VM's but other models as well such as Racks. It connects with bulk edit custom fields and after I fill required custom fields again it overwrites other custom fields with empty data.
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: 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#4404
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?