-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Labels
status: accepted
This issue has been accepted for implementation
type: feature
Introduction of new functionality to the application
Milestone
Comments
Bumped to v2.11 given the amount of work gating this and a lack of focus for it immediately. |
Blocked by #5926 |
jeremystretch
added a commit
that referenced
this issue
Mar 5, 2021
Closes #4999: Support for dynamic table-based exports
Merged
This was referenced May 28, 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
Environment
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.
The text was updated successfully, but these errors were encountered: