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

Cannot create objects with required custom field #4361

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

Originally created by @nahun on GitHub (Dec 15, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • netbox-docker with latest
  • Python version: 3.9.1
  • NetBox version: 2.10.0

Steps to Reproduce

  1. Create a new instance of Netbox using the "latest" build of netbox-docker. The quickstart commands are good.
  2. Create a new Text custom field for DCIM > Device. Mark it required.
  3. Create a new Device, enter anything for the required fields.
  4. Type some text in the required custom field.
  5. Create

Expected Behavior

The device be created

Observed Behavior

Error creating the device: Missing required custom field 'test'.
image

If you mark the custom field as not required, then it takes the value and works fine.

Originally created by @nahun on GitHub (Dec 15, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reporting reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * netbox-docker with latest * Python version: 3.9.1 * NetBox version: 2.10.0 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Create a new instance of Netbox using the "latest" build of netbox-docker. The quickstart commands are good. 2. Create a new Text custom field for DCIM > Device. Mark it required. 3. Create a new Device, enter anything for the required fields. 4. Type some text in the required custom field. 5. Create <!-- What did you expect to happen? --> ### Expected Behavior The device be created <!-- What happened instead? --> ### Observed Behavior Error creating the device: `Missing required custom field 'test'.` ![image](https://user-images.githubusercontent.com/690651/102265493-07338700-3ecc-11eb-8d53-743569d67405.png) If you mark the custom field as not required, then it takes the value and works fine.
adam added the type: bugstatus: accepted labels 2025-12-29 18:35:11 +01:00
adam closed this issue 2025-12-29 18:35:11 +01:00
adam commented 2025-12-29 18:35:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 15, 2020):

Create a new instance of Netbox using the "latest" build of netbox-docker. The quickstart commands are good.

Please note that bug reports must provide reproduction steps using only the stock code base: We do not support the Docker image.

@jeremystretch commented on GitHub (Dec 15, 2020): > Create a new instance of Netbox using the "latest" build of netbox-docker. The quickstart commands are good. Please note that bug reports must provide reproduction steps using only the stock code base: We do not support the Docker image.
adam commented 2025-12-29 18:35:12 +01:00
Author
Owner
Copy Link

@nahun commented on GitHub (Dec 15, 2020):

Sorry about that, and thanks for the fix!

@nahun commented on GitHub (Dec 15, 2020): Sorry about that, and thanks for the fix!
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#4361
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?