Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object list export should match the current table view #4999

Closed
jeremystretch opened this issue Aug 13, 2020 · 2 comments
Closed

Object list export should match the current table view #4999

jeremystretch opened this issue Aug 13, 2020 · 2 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@jeremystretch
Copy link
Member

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.9

Proposed Functionality

Rework the built-in CSV export functionality to export only the data shown in the table, with the columns in the same order.

Use Case

Following the implementation of #492, users are now able to customize object lists by adding, removing, and rearranging table columns. However, the default CSV export for each model is static and does not change. Allowing the CSV export to dynamically adapt along with the table display provides a more consistent user experience and obviates the need for writing custom export templates for minor changes. We also may be able to leverage the built-in export functionality that django-tables2 provides.

Database Changes

None

External Dependencies

tablib will be required if we opt to use django-tables2's export functionality.

@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Aug 13, 2020
@jeremystretch jeremystretch added this to the v2.10 milestone Aug 20, 2020
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Sep 2, 2020
@ryanmerolle ryanmerolle modified the milestones: v2.10, v2.11 Oct 13, 2020
@ryanmerolle
Copy link
Contributor

Bumped to v2.11 given the amount of work gating this and a lack of focus for it immediately.

@jeremystretch
Copy link
Member Author

Blocked by #5926

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: blocked Another issue or external requirement is preventing implementation labels Mar 5, 2021
@jeremystretch jeremystretch self-assigned this Mar 5, 2021
jeremystretch added a commit that referenced this issue Mar 5, 2021
jeremystretch added a commit that referenced this issue Mar 5, 2021
Closes #4999: Support for dynamic table-based exports
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants