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

Cannot update information using import feature #1418

New Issue
Closed
opened 2025-12-29 16:32:06 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:32:06 +01:00
Owner
Copy Link

Originally created by @jjangmoo on GitHub (Nov 23, 2017).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.2

Description

I would like to update information such as platform, tenant or position at one time.
It means I would like to use the import function when I update data.

I think this import function is only working when I want to import new devices.
But I need to update this information on multiple devices.

What do you think about adding a flag field like import_role(value = new or update) in import format?

Originally created by @jjangmoo on GitHub (Nov 23, 2017). ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 3.5.2 * NetBox version: 2.2.2 ### Description I would like to update information such as platform, tenant or position at one time. It means I would like to use the import function when I update data. I think this import function is only working when I want to import new devices. But I need to update this information on multiple devices. What do you think about adding a flag field like import_role(value = new or update) in import format?
adam closed this issue 2025-12-29 16:32:06 +01:00
adam commented 2025-12-29 16:32:06 +01:00
Author
Owner
Copy Link

@Senetus commented on GitHub (Nov 23, 2017):

Optimally, after an initial import, you would use the API to import new devices. But I do agree that having an ignore existing option while doing csv import would be great.

@Senetus commented on GitHub (Nov 23, 2017): Optimally, after an initial import, you would use the API to import new devices. But I do agree that having an ignore existing option while doing csv import would be great.
adam commented 2025-12-29 16:32:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 27, 2017):

CSV import does not allow for modifying existing objects. NetBox provides a separate "bulk update" mechanism for most objects, or you can use the API as @esajo suggested.

@jeremystretch commented on GitHub (Nov 27, 2017): CSV import does not allow for modifying existing objects. NetBox provides a separate "bulk update" mechanism for most objects, or you can use the API as @esajo suggested.
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
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#1418
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?