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 information to CSV Import of cables #11360

New Issue
Closed
opened 2025-12-29 21:44:10 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:44:10 +01:00
Owner
Copy Link

Originally created by @linuxpete on GitHub (Jul 9, 2025).

Originally assigned to: @pheus on GitHub.

NetBox version

v4.3.3

Feature type

Change to existing functionality

Proposed functionality

In my database I have a Devices that have the same Name in different Sites.

When I want to import cables with CSV i can not give a Site name to destination A or B (see netbox_cables_import_test_now.csv )
netbox_cables_import_test_now.csv

Either I have to give a device an elaborate name ( as in "asset tag" in the image below) or add the connectors manually.

Image

Use case

Add to the import variables the fields side_a_site and side_b_site like in the file :

netbox_cables_import_test.csv

So I can import cables to devices with the same name but in different sites.

Database changes

none

External dependencies

unknown

Originally created by @linuxpete on GitHub (Jul 9, 2025). Originally assigned to: @pheus on GitHub. ### NetBox version v4.3.3 ### Feature type Change to existing functionality ### Proposed functionality In my database I have a Devices that have the same Name in different Sites. When I want to import cables with CSV i can not give a Site name to destination A or B (see netbox_cables_import_test_now.csv ) [netbox_cables_import_test_now.csv](https://github.com/user-attachments/files/21141425/netbox_cables_import_test_now.csv) Either I have to give a device an elaborate name ( as in "asset tag" in the image below) or add the connectors manually. <img width="1904" height="333" alt="Image" src="https://github.com/user-attachments/assets/c310ed5e-b646-4db8-8260-8153a6cc3cf5" /> ### Use case Add to the import variables the fields side_a_site and side_b_site like in the file : [netbox_cables_import_test.csv](https://github.com/user-attachments/files/21141483/netbox_cables_import_test.csv) So I can import cables to devices with the same name but in different sites. ### Database changes none ### External dependencies unknown
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:44:10 +01:00
adam closed this issue 2025-12-29 21:44:10 +01:00
adam commented 2025-12-29 21:44:11 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Jul 21, 2025):

I'd like to contribute this enhancement. Can you please assign it to me?

@pheus commented on GitHub (Jul 21, 2025): I'd like to contribute this enhancement. Can you please assign it to me?
adam commented 2025-12-29 21:44:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 21, 2025):

Assigned to you @pheus, thanks!

@jeremystretch commented on GitHub (Jul 21, 2025): Assigned to you @pheus, thanks!
adam commented 2025-12-29 21:44:11 +01:00
Author
Owner
Copy Link

@mkarel commented on GitHub (Jul 30, 2025):

@jnovinger and @pheus This is awesome! I wonder if it should be expanded to include other objects where device names are required. I have run into issues due to the same device name being in the multiple sites and having to reference the device id when doing bulk update / imports.

@mkarel commented on GitHub (Jul 30, 2025): @jnovinger and @pheus This is awesome! I wonder if it should be expanded to include other objects where device names are required. I have run into issues due to the same device name being in the multiple sites and having to reference the device id when doing bulk update / imports.
adam commented 2025-12-29 21:44:12 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Aug 5, 2025):

@mkarel Glad to hear this is helpful for you! You’re absolutely right - expanding this to other objects could improve the bulk import experience even further. Since any potential implementation would need a GitHub issue to track it, feel free to open new issues for the specific cases where you’d like to see this applied. If accepted, I’d be happy to take a look!

@pheus commented on GitHub (Aug 5, 2025): @mkarel Glad to hear this is helpful for you! You’re absolutely right - expanding this to other objects could improve the bulk import experience even further. Since any potential implementation would need a GitHub issue to track it, feel free to open new issues for the specific cases where you’d like to see this applied. If accepted, I’d be happy to take a look!
adam commented 2025-12-29 21:44:12 +01:00
Author
Owner
Copy Link

@linuxpete commented on GitHub (Aug 11, 2025):

Hi All,

Sorry for being toooooo late as raiser of this issue but : Thanks for the work. I checked this morning and it works for me.

Taking my 🎩 off.

Regards, Pieter

@linuxpete commented on GitHub (Aug 11, 2025): Hi All, Sorry for being toooooo late as raiser of this issue but : Thanks for the work. I checked this morning and it works for me. Taking my 🎩 off. Regards, Pieter
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 complexity: low status: accepted 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#11360
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?