Bulk CSV Import for cables with multiple terminations #6965

Closed
opened 2025-12-29 19:47:14 +01:00 by adam · 5 comments
Owner

Originally created by @clatini on GitHub (Sep 11, 2022).

NetBox version

v.3.3.2

Feature type

Change to existing functionality

Proposed functionality

At this time there is no way to bulk import cables when one or both sides have multiple terminations

Use case

for example, adding a special separator in 'device_x_name' column, for example a '|':

side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name
Switch1,dcim.interface,Eth1,PatchPanel1,dcim.frontport,port1|port2|port3|port4

Database changes

n/a

External dependencies

n/a

Originally created by @clatini on GitHub (Sep 11, 2022). ### NetBox version v.3.3.2 ### Feature type Change to existing functionality ### Proposed functionality At this time there is no way to bulk import cables when one or both sides have multiple terminations ### Use case for example, adding a special separator in 'device_x_name' column, for example a '|': ``` side_a_device,side_a_type,side_a_name,side_b_device,side_b_type,side_b_name Switch1,dcim.interface,Eth1,PatchPanel1,dcim.frontport,port1|port2|port3|port4 ``` ### Database changes n/a ### External dependencies n/a
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:47:14 +01:00
adam closed this issue 2025-12-29 19:47:14 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 12, 2022):

The implementation for this should match whatever approach we use for #7376 as far as the CSV formatting for multiple objects.

@jeremystretch commented on GitHub (Sep 12, 2022): The implementation for this should match whatever approach we use for #7376 as far as the CSV formatting for multiple objects.
Author
Owner

@github-actions[bot] commented on GitHub (Nov 16, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 16, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@jeremystretch commented on GitHub (Dec 15, 2022):

This is probably more viable now that we've implemented JSON/YAML imports for cables under #4347 in NetBox v3.4.

@jeremystretch commented on GitHub (Dec 15, 2022): This is probably more viable now that we've implemented JSON/YAML imports for cables under #4347 in NetBox v3.4.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 14, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Feb 14, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Mar 17, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Mar 17, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6965