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 column names in data exports match the name for data imports #11249

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

Originally created by @1024834 on GitHub (Jun 3, 2025).

NetBox version

v4.2.5

Feature type

Change to existing functionality

Proposed functionality

Currently, when data for any object is exported with the "Export" button in the WebUI, the columns will have human friendly names like in 1.png. Importing data with such column names will fail however because they must match the name shown in 2.png.

Change the column names in exported data so it matches the respective name to import it.

1.png
Image

2.png
Image

Use case

This saves work when using exported data (i.e. device IDs) to import other data sets and avoids confusion.

Database changes

No response

External dependencies

No response

Originally created by @1024834 on GitHub (Jun 3, 2025). ### NetBox version v4.2.5 ### Feature type Change to existing functionality ### Proposed functionality Currently, when data for any object is exported with the "Export" button in the WebUI, the columns will have human friendly names like in 1.png. Importing data with such column names will fail however because they must match the name shown in 2.png. Change the column names in exported data so it matches the respective name to import it. **1.png** ![Image](https://github.com/user-attachments/assets/c8a40791-108b-4484-bc5c-a79701b17400) **2.png** ![Image](https://github.com/user-attachments/assets/ddfb6339-bb06-465c-9b55-ef1692f4c252) ### Use case This saves work when using exported data (i.e. device IDs) to import other data sets and avoids confusion. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:42:26 +01:00
adam closed this issue 2025-12-29 21:42:27 +01:00
adam commented 2025-12-29 21:42:27 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 5, 2025):

This is explained in the relevant FAQ entry.

@jnovinger commented on GitHub (Jun 5, 2025): This is explained in the [relevant FAQ entry](https://github.com/netbox-community/netbox/wiki/Frequently-Asked-Questions#why-cant-i-pass-exported-data-directly-into-the-import-form).
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#11249
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?