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

Import Failure Handling #135

New Issue
Closed
opened 2025-12-29 15:34:46 +01:00 by adam · 2 comments
adam commented 2025-12-29 15:34:46 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Jul 1, 2016).

I am testing much of the functionality here and I noticed that if I import records using the csv format, the tool fails on the whole import.

Would it be useful for it to succeed on what it can and report out status of failed (with the current error details) vs successful entries?

Originally created by @ryanmerolle on GitHub (Jul 1, 2016). I am testing much of the functionality here and I noticed that if I import records using the csv format, the tool fails on the whole import. Would it be useful for it to succeed on what it can and report out status of failed (with the current error details) vs successful entries?
adam closed this issue 2025-12-29 15:34:46 +01:00
adam commented 2025-12-29 15:34:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 2, 2016):

CSV import is intentionally all-or-none. Imagine you're importing a hundred interface connections. NetBox gets halfway through and finds an error. If it didn't roll back the transaction, you'd be stuck with half of your connections created and the other half still missing. This would require you to delete all of the successfully imported connections before attempting another import.

It's a lot simpler IMO to just fix the error and try re-importing the whole batch again, especially when you're exporting to CSV from Google Sheets or Excel.

@jeremystretch commented on GitHub (Jul 2, 2016): CSV import is intentionally all-or-none. Imagine you're importing a hundred interface connections. NetBox gets halfway through and finds an error. If it didn't roll back the transaction, you'd be stuck with half of your connections created and the other half still missing. This would require you to delete all of the successfully imported connections before attempting another import. It's a lot simpler IMO to just fix the error and try re-importing the whole batch again, especially when you're exporting to CSV from Google Sheets or Excel.
adam commented 2025-12-29 15:34:48 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jul 2, 2016):

Thanks for the insight into your thought process!

@ryanmerolle commented on GitHub (Jul 2, 2016): Thanks for the insight into your thought process!
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#135
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?