Skip to content

Bulk import throws exception when certain custom field attributes are defined #19117

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.

Sign up for GitHub

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

Jump to bottom
Open
atownson opened this issue Apr 8, 2025 · 0 comments · May be fixed by #19119
Open

Bulk import throws exception when certain custom field attributes are defined #19117

atownson opened this issue Apr 8, 2025 · 0 comments · May be fixed by #19119
Assignees
@jnovinger
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
v4.2.9

Comments

@atownson
Copy link
Contributor

atownson commented Apr 8, 2025

Deployment Type

NetBox Cloud

NetBox Version

v4.2.6

Python Version

3.12

Steps to Reproduce

  1. Add a custom field named "my_cf_field" to the model Site (or any other model) of Type "Multiple object" - set as not required, enter [1,2] as the Default value, and set Related object type to Region (or any other model).
  2. Ensure that at least 2 Regions exist (with IDs of 1 and 2) - to populate the default values
  3. Attempt to bulk import a Site with the following payload:
name,slug,status
My Site,my-site,active

Expected Behavior

The site is created and the custom field "my_cf_field" is set to the default of Regions with IDs 1 and 2.

Observed Behavior

An exception is thrown: 'list' object has no attribute 'split'
The exception location is /opt/netbox/netbox/utilities/forms/fields/csv.py, line 82, in clean
@atownson atownson 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 8, 2025
@jnovinger jnovinger added status: accepted This issue has been accepted for 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 8, 2025
@jnovinger jnovinger self-assigned this Apr 8, 2025
@jnovinger jnovinger added this to the v4.2.7 milestone Apr 8, 2025
@jnovinger jnovinger linked a pull request Apr 8, 2025 that will close this issue
Draft
@jeremystretch jeremystretch modified the milestones: v4.2.7, v4.2.8 Apr 10, 2025
@jeremystretch jeremystretch modified the milestones: v4.2.8, v4.2.9 Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jnovinger jnovinger

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
Milestone
v4.2.9
3 participants
@jnovinger @jeremystretch @atownson