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

Make bulk import/update header fields case-insensitive #8617

New Issue
Closed
opened 2025-12-29 20:38:58 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:38:58 +01:00
Owner
Copy Link

Originally created by @peteeckel on GitHub (Sep 15, 2023).

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

Based on the brief discussion of #13773 I suggest that the handling of the header line in bulk import/update should be case insensitive.

Use case

This would avoid a couple of apparently common cases where data is silently ignored because of casing, which is often introduced when data from an export is converted to input data.

Database changes

None

External dependencies

None

Originally created by @peteeckel on GitHub (Sep 15, 2023). ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality Based on the brief discussion of #13773 I suggest that the handling of the header line in bulk import/update should be case insensitive. ### Use case This would avoid a couple of apparently common cases where data is silently ignored because of casing, which is often introduced when data from an export is converted to input data. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 20:38:58 +01:00
adam closed this issue 2025-12-29 20:38:58 +01:00
adam commented 2025-12-29 20:38:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 15, 2023):

This would work for all built-in model fields, but it's not currently feasible for custom fields as we don't enforce case insensitivity on custom field names. For example, a model could have custom fields named foo and Foo. It's a terrible idea, of course, however it is currently a valid scenario.

@jeremystretch commented on GitHub (Sep 15, 2023): This would work for all built-in model fields, but it's not currently feasible for custom fields as we don't enforce case insensitivity on custom field names. For example, a model could have custom fields named `foo` and `Foo`. It's a terrible idea, of course, however it is currently a valid scenario.
adam commented 2025-12-29 20:38:59 +01:00
Author
Owner
Copy Link

@peteeckel commented on GitHub (Sep 15, 2023):

Yuck. Well, once the PR for #11617 is implemented that won't be as much of an issue anymore either, so never mind.

@peteeckel commented on GitHub (Sep 15, 2023): Yuck. Well, once the PR for #11617 is implemented that won't be as much of an issue anymore either, so never mind.
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#8617
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?