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

Export data with lowercase field name #5338

New Issue
Closed
opened 2025-12-29 19:26:52 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:26:52 +01:00
Owner
Copy Link

Originally created by @Theprim0 on GitHub (Sep 8, 2021).

NetBox version

v3.0.1

Feature type

Data model extension

Proposed functionality

Is it possible to change the export option to export fields with lowercase names? Because when importing, it needs to be lowercase but it actually exports it with uppercase.
Example:

Name,Status,Tenant,Role,Manufacturer,Type,Platform,Serial number

But it requests the following to import:

name,status,tenant,role,manufacturer,type,platform,serial number,

Something like this also occurs to fileds like "Active", it exports with uppercase but when importing it needs lowecase "active"

Use case

This will benefit when migrating data

Database changes

No response

External dependencies

No response

Originally created by @Theprim0 on GitHub (Sep 8, 2021). ### NetBox version v3.0.1 ### Feature type Data model extension ### Proposed functionality Is it possible to change the export option to export fields with lowercase names? Because when importing, it needs to be lowercase but it actually exports it with uppercase. Example: Name,Status,Tenant,Role,Manufacturer,Type,Platform,Serial number But it requests the following to import: name,status,tenant,role,manufacturer,type,platform,serial number, Something like this also occurs to fileds like "Active", it exports with uppercase but when importing it needs lowecase "active" ### Use case This will benefit when migrating data ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:26:52 +01:00
adam closed this issue 2025-12-29 19:26:52 +01:00
adam commented 2025-12-29 19:26:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 8, 2021):

Exported data is generated to match the current table view, including the headers. This will not be changed. However, you're free to create a custom export template to export data in whatever format you'd like.

@jeremystretch commented on GitHub (Sep 8, 2021): Exported data is generated to match the current table view, including the headers. This will not be changed. However, you're free to create a custom [export template](https://netbox.readthedocs.io/en/stable/customization/export-templates/) to export data in whatever format you'd like.
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#5338
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?