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

Datatable columns should have option for exporting #2945

Closed
pantonis opened this issue May 31, 2017 · 3 comments
Closed

Datatable columns should have option for exporting #2945

pantonis opened this issue May 31, 2017 · 3 comments

Comments

@pantonis
Copy link
Contributor

pantonis commented May 31, 2017

I'm submitting a ... (check one with "x")

[ ] bug report => Search github for a similar issue or PR before submitting
[X ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Current behavior
When working with Datatable and use export functionality all columns are exported and there is no option (attribute) to exclude a column from exporting.

  • Angular version:
    4.0.3

  • PrimeNG version:
    4.0.2

@kenisteward
Copy link

dupe #1567 @cagataycivici

Also is there a roadmap / changelog somewhere? I'm considering contributing export changes but don't know where I can.

@cagataycivici
Copy link
Member

Duplicate yes, please see wiki for roadmap.

@kenisteward
Copy link

kenisteward commented Jun 22, 2017

@cagataycivici Ahh I see
DataTable

More export options like pdf and excel
State saving featuring across views
Cell Selection
Frozen Rows

is planned and i see that might be for 4.1.1 but I don't know how long major/minor patches take.

As a part of it I would also suggest an onExport callback be created in order to change the way the field is exported as well as changing the default export to use JSON.stringify() because currently objects are exported as [object: OBJECT] unless you explicitly implement .toString()

Also the csvSeparator field currently work the way you'd expect. yes it adds the separator in between each field but it does not at sep={yourSeparator} to the top of the file (as most csv parsers like excel would expect)

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

No branches or pull requests

3 participants