Skip to content
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

CSV import for custom fields of Multiple Object type does not work #11711

Closed
kkthxbye-code opened this issue Feb 9, 2023 · 0 comments · Fixed by #11712
Closed

CSV import for custom fields of Multiple Object type does not work #11711

kkthxbye-code opened this issue Feb 9, 2023 · 0 comments · Fixed by #11712
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@kkthxbye-code
Copy link
Contributor

NetBox version

v3.4.4

Python version

3.10

Steps to Reproduce

  1. Create a CircuitType and Circuit, get the ID of the circuit
  2. Create a customfield of multiple object type named cf_tenantmulti
  3. Try to import the following:
name,slug,cf_tenantmulti
test1233dsdsfdsfdsffdsf21,testdsfsdfdsfddsfdsfsfsdfsdf,1

Expected Behavior

Import succeed

Observed Behavior

Row 1 cf_tenantmulti: Enter a list of values

@kkthxbye-code kkthxbye-code added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation labels Feb 9, 2023
@kkthxbye-code kkthxbye-code self-assigned this Feb 9, 2023
kkthxbye-code pushed a commit to kkthxbye-code/netbox that referenced this issue Feb 9, 2023
jeremystretch pushed a commit that referenced this issue Feb 13, 2023
…multiple object fields (#11712)

* Fixes #11711 - Use CSVModelMultipleChoiceField when importing custom multiple object fields

* Fix pep8

---------

Co-authored-by: kkthxbye-code <>
jeremystretch added a commit that referenced this issue Feb 13, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
1 participant