Porblem with Cable Bulk Import/export #4194

Closed
opened 2025-12-29 18:33:47 +01:00 by adam · 3 comments
Owner

Originally created by @TheKingOfChaos on GitHub (Oct 16, 2020).

Environment

  • Python version: python 3.6
  • NetBox version: v2.9.4

Steps to Reproduce

  1. use the cable Export function
  2. take the file and use the Cable Bulk Import

Expected Behavior

the Expected was that i can use the export and import the data back

Observed Behavior

the fieldt names of the import and export is not compatible

Originally created by @TheKingOfChaos on GitHub (Oct 16, 2020). ### Environment * Python version: python 3.6 * NetBox version: v2.9.4 ### Steps to Reproduce 1. use the cable Export function 2. take the file and use the Cable Bulk Import <!-- What did you expect to happen? --> ### Expected Behavior the Expected was that i can use the export and import the data back <!-- What happened instead? --> ### Observed Behavior the fieldt names of the import and export is not compatible
adam added the status: duplicate label 2025-12-29 18:33:47 +01:00
adam closed this issue 2025-12-29 18:33:47 +01:00
Author
Owner

@jeremystretch commented on GitHub (Oct 16, 2020):

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@jeremystretch commented on GitHub (Oct 16, 2020): Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the [feature request template](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.
Author
Owner

@martink2 commented on GitHub (Oct 17, 2020):

We ran into the same issue. Using Export on cables gives a CSV with
the following headers:

termination_a_type,termination_a_id,termination_b_type,termination_b_id,type,status,label,color,length,length_unit

But the import for cables expects:

side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name

Which means when you want to import the data back you need to rename the headers and replace all device id's with the device names.

@martink2 commented on GitHub (Oct 17, 2020): We ran into the same issue. Using Export on cables gives a CSV with the following headers: `termination_a_type,termination_a_id,termination_b_type,termination_b_id,type,status,label,color,length,length_unit` But the import for cables expects: `side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name` Which means when you want to import the data back you need to rename the headers and replace all device id's with the device names.
Author
Owner

@jeremystretch commented on GitHub (Oct 19, 2020):

Duplicate of #4429. Please note that this is expected behavior, as the CSV import fields are customizable.

@jeremystretch commented on GitHub (Oct 19, 2020): Duplicate of #4429. Please note that this is expected behavior, as the CSV import fields are customizable.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4194