starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add the ability to select the format for exporting object data #11381

New Issue
Closed
opened 2025-12-29 21:44:26 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:44:26 +01:00
Owner
Copy Link

Originally created by @shoksdev on GitHub (Jul 14, 2025).

NetBox version

4.3.3

Feature type

Change to existing functionality

Proposed functionality

Hello! I suggest in the export_table function, ObjectListView class, line 96
change (export_format=TableExport.CSV)
to export_format=export_format
the export_format variable will be passed as an argument to the function. Or you can add the ability to export to Excel, directly to the drop-down list, along with export to CSV. It is also quite easy to implement, as django_tables2 supports different export formats.

Use case

This innovation will expand the possibilities of developing plugins for NetBox, and will also increase the number of exported formats. Because one CSV is not always enough and it is much more convenient to study information from export in Excel.

Database changes

External dependencies

Originally created by @shoksdev on GitHub (Jul 14, 2025). ### NetBox version 4.3.3 ### Feature type Change to existing functionality ### Proposed functionality Hello! I suggest in the export_table function, ObjectListView class, line 96 change (export_format=TableExport.CSV) to export_format=export_format the export_format variable will be passed as an argument to the function. Or you can add the ability to export to Excel, directly to the drop-down list, along with export to CSV. It is also quite easy to implement, as django_tables2 supports different export formats. ### Use case This innovation will expand the possibilities of developing plugins for NetBox, and will also increase the number of exported formats. Because one CSV is not always enough and it is much more convenient to study information from export in Excel. ### Database changes - ### External dependencies -
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:44:26 +01:00
adam closed this issue 2025-12-29 21:44:26 +01:00
adam commented 2025-12-29 21:44:26 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jul 15, 2025):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

  1. In particular, what do you mean "export to Excel", as opposed to CSV? How would that differ from CSV other than the file formatting bits?
  2. Also, how would export_format be passed in to export_table()? Where would the value come from?
  3. How would this feature improve developing plugins for NetBox?
  4. How is one CSV (for a single list of a single kind of item) not sufficient? Why can't you study CSV exports in Excel?

Please be specific and complete.

@jnovinger commented on GitHub (Jul 15, 2025): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed. 1. In particular, what do you mean "export to Excel", as opposed to CSV? How would that differ from CSV other than the file formatting bits? 2. Also, how would `export_format` be passed in to `export_table()`? Where would the value come from? 3. How would this feature improve developing plugins for NetBox? 4. How is one CSV (for a single list of a single kind of item) not sufficient? Why can't you study CSV exports in Excel? Please be specific and complete.
adam commented 2025-12-29 21:44:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 23, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Jul 23, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:44:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 30, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jul 30, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 pending closure status: revisions needed 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#11381
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?