-
Notifications
You must be signed in to change notification settings - Fork 161
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
Export Hierarchical Grid to Excel #5848
Comments
Hi there, just jumping in because this would be really helpful for us too For info, the workaround I did is to flatten the data and export it as a single array (which might not meet some requirements) |
There has been no recent activity and this issue has been marked inactive. |
There has been no recent activity and this issue has been marked inactive. |
There has been no recent activity and this issue has been marked inactive. |
There has been no recent activity and this issue has been marked inactive. |
up to avoid automatic closing :) |
Hi, |
@bmtheo @senkron-dev the feature could be planned for the next milestone ,starting end of Feb. I will update you next week on the possible ETA. |
Thank for the info, |
@senkron-dev, I can confirm the feature is included in the roadmap, ETA - 19th Apr. It could be available sooner in alpha release. |
Is your feature request related to a problem? Please describe.
The igxHierarchicalGrid cannot be exported to Excel
Describe the solution you'd like
Export hierarchical grid in Angular to Excel, as by hierarchical grid in jQuery.
Describe alternatives you've considered
The Excel Exporter is not generic enough
The Excel Exporter is not generic, i.e it's so much dependent on the type of the grid, the data originates from. That may cause trouble and is not flexible.
There are not enough exposed properties in the Exporter Service API
If the user wants to export data, which looks somehow different from the already implemented logics, one may not succeed, because of lack of enough handlers.
Reference
Exporter Service API
The text was updated successfully, but these errors were encountered: