starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add Site Field To Cable Bulk Import From CSV #5532

New Issue
Closed
opened 2025-12-29 19:29:04 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:29:04 +01:00
Owner
Copy Link

Originally created by @dtaylor-habana on GitHub (Oct 18, 2021).

NetBox version

v3.0.5

Feature type

Change to existing functionality

Proposed functionality

Currently, when importing cable connections from a CSV file, the CSV doesn't allow for an optional flag for what site the cable/device is at.

The proposed functionality would be to add an optional (or required) flag to specify what site each device is at. This will resolve cases where two devices will have the same name at different sites.

This functionality should also be extended to the API as there doesn't seem to be any site specification when creating cable connections via the API either.

Use case

We have a device called C10U42N at Site A, and a device with the same name at Site B.

When using the Cable Bulk Import function, I specify C10L (side_a_device) as being connected to C10U42N (side_b_device). Both devices are located at Site A, however Netbox doesn't know whether I'm referencing Site A or Site B when specifying C10U42N in the bulk import.

Database changes

There may be a requirement for this change to add "side_a_site" and "side_b_site" fields to cable connections, but this may already exist as individual devices have a "site" field associated with them.

External dependencies

No response

Originally created by @dtaylor-habana on GitHub (Oct 18, 2021). ### NetBox version v3.0.5 ### Feature type Change to existing functionality ### Proposed functionality Currently, when importing cable connections from a CSV file, the CSV doesn't allow for an optional flag for what site the cable/device is at. The proposed functionality would be to add an optional (or required) flag to specify what site each device is at. This will resolve cases where two devices will have the same name at different sites. This functionality should also be extended to the API as there doesn't seem to be any site specification when creating cable connections via the API either. ### Use case We have a device called C10U42N at Site A, and a device with the same name at Site B. When using the Cable Bulk Import function, I specify C10L (side_a_device) as being connected to C10U42N (side_b_device). Both devices are located at Site A, however Netbox doesn't know whether I'm referencing Site A or Site B when specifying C10U42N in the bulk import. ### Database changes There may be a requirement for this change to add "side_a_site" and "side_b_site" fields to cable connections, but this may already exist as individual devices have a "site" field associated with them. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:29:04 +01:00
adam closed this issue 2025-12-29 19:29:04 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5532
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?