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

Export to CSV from a dashboard is not consistent with Discover CSV behavior #34376

Closed
AlonaNadler opened this issue Apr 2, 2019 · 6 comments · Fixed by #88303
Closed

Export to CSV from a dashboard is not consistent with Discover CSV behavior #34376

AlonaNadler opened this issue Apr 2, 2019 · 6 comments · Fixed by #88303
Labels
bug Fixes for quality problems that affect the customer experience Feature:Reporting:CSV Reporting issues pertaining to CSV file export needs-team Issues missing a team label

Comments

@AlonaNadler
Copy link

AlonaNadler commented Apr 2, 2019

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

@AlonaNadler AlonaNadler added bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Apr 2, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 2019
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@tsullivan
Copy link
Member

tsullivan commented Dec 12, 2019

where no fields were added explicitly it export all fields to the CSV

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.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServices)

@tsullivan tsullivan removed the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Dec 17, 2020
@tsullivan
Copy link
Member

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan
Copy link
Member

Duplicate of #68718

@tsullivan tsullivan marked this as a duplicate of #68718 Feb 25, 2021
@sophiec20 sophiec20 added Feature:Reporting:CSV Reporting issues pertaining to CSV file export and removed (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead (Deprecated) Team:Reporting Services labels Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Reporting:CSV Reporting issues pertaining to CSV file export needs-team Issues missing a team label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants