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

Update CSV Import field options description #6972

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

Originally created by @ghost on GitHub (Sep 12, 2022).

NetBox version

v3.3.2

Feature type

Change to existing functionality

Proposed functionality

https://github.com/netbox-community/netbox/discussions/10326

Please update the 'field' Header for all import field option pages from 'Field' to 'Field (case-sensitive)'
This will inform users that when importing either via copy+paste, or CSV file import, that field names in netbox are case sensitive.
Please see above discussion for screenshot of proposed change and why this change would help users better understand how to import data into netbox.

Use case

When trying to import data, if you have a field called 'Name' the import process will fail. There is no current documentation that mentions the field names are case sensitive and can cause user frustration.

Database changes

none

External dependencies

none

Originally created by @ghost on GitHub (Sep 12, 2022). ### NetBox version v3.3.2 ### Feature type Change to existing functionality ### Proposed functionality https://github.com/netbox-community/netbox/discussions/10326 Please update the 'field' Header for all import field option pages from 'Field' to 'Field (case-sensitive)' This will inform users that when importing either via copy+paste, or CSV file import, that field names in netbox are case sensitive. Please see above discussion for screenshot of proposed change and why this change would help users better understand how to import data into netbox. ### Use case When trying to import data, if you have a field called 'Name' the import process will fail. There is no current documentation that mentions the field names are case sensitive and can cause user frustration. ### Database changes none ### External dependencies none
adam added the type: featuretopic: UI/UX labels 2025-12-29 19:47:21 +01:00
adam closed this issue 2025-12-29 19:47:21 +01:00
adam commented 2025-12-29 19:47:21 +01:00
Author
Owner
Copy Link

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

There is no current documentation that mentions the field names are case sensitive and can cause user frustration.

The documentation provided on every CSV import form tells you exactly what the field headings should be. Your confusion in #10362 arose from trying to reverse engineer the column headings from a CSV export, rather than following the prescribed format.

@jeremystretch commented on GitHub (Sep 15, 2022): > There is no current documentation that mentions the field names are case sensitive and can cause user frustration. The documentation provided on every CSV import form tells you exactly what the field headings should be. Your confusion in #10362 arose from trying to reverse engineer the column headings from a CSV export, rather than following the prescribed format.
adam commented 2025-12-29 19:47:22 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 15, 2022):

Jeremy, did you not read the thread about this issue that I linked to.
Just because you say the field name is 'name' in the CSV import form doesn't mean it can't be BETTER documented.
Why do you refuse to add additional information to help users? Especially something as low effort as adding '(case-sensitive)' next to a field header? I just don't get it.

@ghost commented on GitHub (Sep 15, 2022): Jeremy, did you not read the thread about this issue that I linked to. Just because you say the field name is 'name' in the CSV import form doesn't mean it can't be BETTER documented. Why do you refuse to add additional information to help users? Especially something as low effort as adding '(case-sensitive)' next to a field header? I just don't get it.
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 topic: UI/UX 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#6972
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?