Skip to content

"base_choices" is not working in custom field choice bulk import #19166

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jordihelp opened this issue Apr 14, 2025 · 0 comments · Fixed by #19257
Closed

"base_choices" is not working in custom field choice bulk import #19166

jordihelp opened this issue Apr 14, 2025 · 0 comments · Fixed by #19257
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone

Comments

@jordihelp
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.2.6

Python Version

3.11

Steps to Reproduce

  1. Click in "Bulk import" in "Custom Field Choices"
  2. Set data to:
---
name: Choices
description: 
order_alphabetically: False
base_choices: ISO_3166
extra_choices: 
  1. Set format to YAML
  2. Click "Submit" button

Expected Behavior

A new custom field choice should have been created with the selected base choices.

Observed Behavior

An error "Must define base or extra choices" was raised

@jordihelp jordihelp added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Apr 14, 2025
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 15, 2025
@jeremystretch jeremystretch self-assigned this Apr 22, 2025
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Apr 22, 2025
@jeremystretch jeremystretch added this to the v4.2.8 milestone Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants