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

Let user select how many records / rows to export when clicking for example CSV export #8314

mattab opened this Issue Jul 9, 2015 · 0 comments


None yet
1 participant

mattab commented Jul 9, 2015

Currently, when exporting a data set in Piwik, it will export the current number of records displayed on screen. By default most tables show 10 rows so the export, so when exporting data, the URL has &filter_limit=10 and only 10 rows are exported. One can manually change this value in the URL. But this is not intuitive and many users would not know to do this.

For example we got this feedback via the feedback tool:

This isn't just with the Visitor Log but anywhere that has an export feature to CSV for example. Currently I have it set to 25 and I realize it can go to 500. But what if I wanted to export more than that, let's say all the data that is available for a particular range. I don't want to scroll to each page, even if it is 10 pages by 500 items per page. I think there should be an option to export all the data for the current Data Range you are working in.

Maybe when a user clicks an export link (eg. CSV) we could show a little popover or some other mechanism, that lets user select how many rows should be exported. One could then choose to export 50, 500 or even "all" records.

@mattab mattab added this to the Mid term milestone Jul 15, 2015

@mattab mattab added duplicate and removed Major labels Dec 5, 2016

@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016

@mattab mattab removed the duplicate label Dec 5, 2016

@mattab mattab modified the milestones: Backlog (Help wanted), 3.3.0 Dec 15, 2017

@mattab mattab modified the milestones: 3.5.0, 3.4.0 Mar 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment