Device CSV import doesn't support exported CSV (rack_name) #5210

Closed
opened 2025-12-29 19:25:28 +01:00 by adam · 3 comments
Owner

Originally created by @m0nkeyc0de on GitHub (Aug 20, 2021).

NetBox version

v2.11.11

Python version

3.8

Steps to Reproduce

Same problem as already described in #5238 but closed due to inactivity

Following error messages appears when I try to import the Device CSV I exported on Netbox:
Unexpected column header "rack_name" found

Steps to reproduce:

  1. Create a device that's in a rack
  2. Export the CSV
  3. Import the CSV in another instance
  4. Enjoy the error message described above

Expected Behavior

All exported fields should be imported

Observed Behavior

Unexpected column header "rack_name" found

Originally created by @m0nkeyc0de on GitHub (Aug 20, 2021). ### NetBox version v2.11.11 ### Python version 3.8 ### Steps to Reproduce Same problem as already described in #5238 but closed due to inactivity Following error messages appears when I try to import the Device CSV I exported on Netbox: Unexpected column header "rack_name" found Steps to reproduce: 1. Create a device that's in a rack 2. Export the CSV 3. Import the CSV in another instance 4. Enjoy the error message described above ### Expected Behavior All exported fields should be imported ### Observed Behavior Unexpected column header "rack_name" found
adam closed this issue 2025-12-29 19:25:28 +01:00
Author
Owner

@jeremystretch commented on GitHub (Aug 20, 2021):

All exported fields should be imported

This is not intended behavior. Please see the CSV import form for the list of supported fields.

@jeremystretch commented on GitHub (Aug 20, 2021): > All exported fields should be imported This is not intended behavior. Please see the CSV import form for the list of supported fields.
Author
Owner

@m0nkeyc0de commented on GitHub (Aug 20, 2021):

Is it a NetBox intended feature to not be able to import it own exports, or just a side-effect ?
A simple solution (at least on user side) could be to just ignore unsupported columns and throw a warning message.

@m0nkeyc0de commented on GitHub (Aug 20, 2021): Is it a NetBox intended feature to not be able to import it own exports, or just a side-effect ? A simple solution (at least on user side) could be to just ignore unsupported columns and throw a warning message.
Author
Owner

@jeremystretch commented on GitHub (Aug 20, 2021):

Is it a NetBox intended feature to not be able to import it own exports

Yes, for various reasons which have been discussed in numerous other issues here.

@jeremystretch commented on GitHub (Aug 20, 2021): > Is it a NetBox intended feature to not be able to import it own exports Yes, for various reasons which have been discussed in numerous other issues here.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5210