Skip to content
This repository has been archived by the owner on Jul 25, 2021. It is now read-only.

It is exporting first page of table only #50

Closed
rameshlekkala opened this issue Mar 24, 2017 · 6 comments
Closed

It is exporting first page of table only #50

rameshlekkala opened this issue Mar 24, 2017 · 6 comments

Comments

@rameshlekkala
Copy link

Hi,

I have a table which has the pagination. It contains 100 pages. This plugin is exporting only first page records. Please help me, I need to export all the records from 100 pages.

Thanks

@clarketm
Copy link
Owner

clarketm commented Apr 28, 2017

@rameshlekkala - I'm going to need some more clarity and context on the implementation before I can address your issue.

@rameshlekkala
Copy link
Author

@clarketm - I created a table from JSON Data using Datatable plugin.
That table contains 100 pages each page contains 25 records. By using this plugin I'm trying to export that complete table data. But it is exporting only first page. That means what ever the records are there from 1 - 25 in first page it is exporting from 25 - 2500 it is not exporting. Now my question is how to export all the pages.

@clarketm
Copy link
Owner

clarketm commented Apr 28, 2017

Hey @rameshlekkala. DataTables and TableExport are more or less substitutes rather than complements. So typically, you would either use one or the other rather than both. Since you are already using DataTables in your project, I would suggest that you leverage the export functionality they offer as an extension to their core library. You can find more information on it on their buttons demo. The reason I suggest this over porting over to TableExport, is simply that until the v4 release, (sometime at the beginning of May if all goes well) there isn't extensible support for blob storage off the DOM node (either LocalStorage or other storage/caching mechanism) or pagination. The browser support for DataTables is basically equivalent to TableExport as well with DataTables offering a flash fallback for legacy browsers. I still think TableExport is a viable, lightweight alternative. Also, I plan to reorient TableExport to be more "future proof" leveraging more modern Web APIs, and modern web development tools, refining the environment and frameworks it can operate with - in addition to a traditional static browser context.

@rameshlekkala
Copy link
Author

@clarketm
Thanks. It really make sense to me. Thanks for detail explanation. I'm able to resolve this issue.

@clarketm clarketm closed this as completed May 2, 2017
@AbdullahiAbdulkabir
Copy link

I have same issues but i used tableexport any help pls?

@rameshlekkala
Copy link
Author

rameshlekkala commented Dec 25, 2018 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants