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

Error rendering form fields for custom fields with a large number of choices #8432

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

Originally created by @jeremystretch on GitHub (Aug 8, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.6-beta1

Python version

3.10

Steps to Reproduce

  1. Create a new custom field choice set, specifying UN/LOCODE as the base choice set and no extra choices.
  2. Create a selection custom field which employs this choice set for the site model. (Any model works.)
  3. Attempt to create a new site.

Expected Behavior

The site creation form should load and include the custom field. Choices for the custom field should be populated on-demand using API-backed pagination to avoid loading too much data at once.

Observed Behavior

The page either times out or takes an excessively long time to load. This is because all choices for the custom field are being included when the form is rendered.

Originally created by @jeremystretch on GitHub (Aug 8, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.6-beta1 ### Python version 3.10 ### Steps to Reproduce 1. Create a new custom field choice set, specifying UN/LOCODE as the base choice set and no extra choices. 2. Create a selection custom field which employs this choice set for the site model. (Any model works.) 3. Attempt to create a new site. ### Expected Behavior The site creation form should load and include the custom field. Choices for the custom field should be populated on-demand using API-backed pagination to avoid loading too much data at once. ### Observed Behavior The page either times out or takes an excessively long time to load. This is because _all_ choices for the custom field are being included when the form is rendered.
adam added the type: bugstatus: acceptedbetaseverity: medium labels 2025-12-29 20:36:38 +01:00
adam closed this issue 2025-12-29 20:36:38 +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 beta severity: medium 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#8432
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?