-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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 to CSV from a dashboard is not consistent with Discover CSV behavior #34376
Comments
Pinging @elastic/kibana-app |
This is a bit of a hidden feature, and currently requires a lot of logic on the front-end to support. The request to generate the report has to be modified on the fly to include every single field from the index pattern. It can easily create a HTTP request with a super large query string that has trouble working in certain infrastructures. I'm not really sure this is a good approach to begin with. |
Pinging @elastic/kibana-app-services (Team:AppServices) |
This will be addressed when CSV Export uses SearchSource on the server internally. This is a priority since it is related to supporting Runtime Fields with CSV Export: #81079 |
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
Duplicate of #68718 |
When you have a saved search without specifying any specific fields the export to CSV from the dashboard exports a CSV with only the date fields, I think it should behave the same as Discover - where no fields were added explicitly it export all fields to the CSV
Related to #33709
The text was updated successfully, but these errors were encountered: