Excel exported is not in the same format in Explore
CompletedHi all,
I am trying to export/schedule a dashboard to users and the report sent out is not displaying the right format as what I am seeing in Explore.
what I expect to be seeing in the excel exported should be similar to this:
Yet the data exported looks like this:
It re-arranges the format of the file (column to row).
Is there anyway that excel exported can be looked exactly the same as what I built in Explore?
Thank you.
-
Official comment
Hi everyone,
We have some good news for you. We have released an update for the Excel exports that ensures that the layout of the attributes stay the same in the Excel exports as it is in the UI. For example, if you place Ticket status on columns in the Explore query builder and export this query in Excel format you will get exactly the same layout where Ticket status stays in the table header.
However, CSV exports will continue using the raw data format where all attributes are moved to the Rows.Explore UI
Excel Export
CSV Export
-
Hello Eugene
I'm having the same issue and to be honest it's not very helpful. Can you explain why, when this worked in Good Data but this is no longer the case with the introduction of Explore, that this is 'expected behaviour' please? Why would transposing the row/columns seem like a good idea?
It makes exporting Zendesk data to be used in conjunction with other sources a problem and is a retrograde step.
Please re-consider the change plans.
-
This subject has been open for over a year now and has been 5 months since any update. With insights going away, this needs to work. How do I explain to upper management that we spend a lot of money on a product that can't even export a report properly? We need an update please.
-
Hi,
I am still waiting for the answer.
-
+1
The way it exports now makes it nearly unusable. GoodData handled exporting well if that functionality can be added to Explore.
-
Any updates on the timeline of when this issue will be resolved?
-
HI everyone!
+1 Like others, i'm patiently waiting for correct exporting tables into excel. Please, give us a message when it will be released. -
Hello!
I would like to add my voice to this post as well. I've recently encountered this shortcoming when trying to export a table report for our finance department and would very much like to see the table export behavior changed.
-
That's not possible! Are you introducing a product that does not export correctly? I think Zendesk wants to be a customer-focused company.
Change this circumstance quickly. In our case this concerns several reports. And an apology should be considered as well. -
Has this issue been resolved? It is extremely painful to build these reports and then not be able to export with the same format. Please advise when this is to be addressed or what the workaround is in Explore and/or Excel?
-
Any update as to if/when this feature will work? Makes it quite difficult to run nice reports and now be able to share them or properly review numbers that excel can do. Insights was a great tool but seems to no longer be active as my reporting numbers no longer change.
-
This does make the reporting useless, for even a small company that spends $70,000 a year for your product. I'd think that you can get a developer on this for the 2 hours it would take. This feature works on insights, why go backwards?
-
+1 from me that this needs to get fixed. I have to do a lot of copying and pasting into other systems for executive reports. Having to export the data to excel (because copying tables out of Explore is awful) and having to remake the report as a pivot table in Excel is painful. Not to mention a big step back from Insights/Good Data.
-
Any updates on this? Your requirements do not appear to be user driven: "One of the goals is to make sure that attributes placed on columns are not moved to rows in the exports" . The only goal we're talking about here from a user point of view is ability to export format along with values.
-
It is strange, we should pay for something but it doesn't work correctly. Waiting for fix
-
This is an issue for our reporting as well. In our case, other internal teams request the exports to integrate with other internal data sources. It seems like a reasonable requirement to match the export view to the report view, or to make this configurable upon export.
The current behavior discourages adoption of Explore and encourages users to export unformatted data to start the report workflow and formatting in Excel or Google sheets.
-
Everyone, thank you for the feedback on this issue. Explore team will be working on improving the exports functionality during this year. One of the goals is to make sure that attributes placed on columns are not moved to rows in the exports.
-
Exporting reports from explore - where you have #Number of tags / ticket topics built per week as columns and tags / topics as rows exports into csv / excel as a single column with same tag / topic repeated with second column showing as numbers. -- Same report in Insights has the columns as per week - as per the query.
Metrics are:
COUNT(TICKETS)
Column:
Tickets Solved - Week of yearRows:
Ticket Tags
Filtered by 2020.
Explore report = OK columns showing okay
Exporting to Excel / csv is not ok.
This needs to be a priority. -- There is no way that columns in explore become a second column in rows. Insights has the same query as
What = Solved Tickets
How = Ticket Tag / Week / year solved
Each week is it's own column with 1 ticket tag per row - and the number of solved tickets. No issues with Insights excel exporting. -
Absolutely agree with all people in this topic.
When export screws the data you see in report/dashboard - it's really unusable.
Please raise this issue priority. -
+1
I've finally been able to transport all my relevant reports from Insights to Explore, but without this working properly, I'll still have to export my reports from Insights. That seems counterproductive. -
Thank you for the great feedback.
Our apologies that we didn't release an update in this area earlier. We are currently working on fixing this issue for Excel exports. Once we will release this update tables exported in Excel format will reflect layout set in the query builder. -
We are also waiting for a fix on this. Zendesk exported our reports into Explore for us; however, I will not sign off on completion of the project until this issue is fixed. I still have to use Insights for printing and exporting. The print functionality is useless. It does not print an entire dashboard. I can not use this to send to our clients or to our executives.
If this isn't fixed by February 5th, I hope you reconsider expiring Insights. It seems several people are still relying on it for printing and exporting to excel. I also have to add that when exporting to excel in Insights, it looked much better.
-
Hi Liam and all, thanks for the feedback about this. Liam, I've created a ticket from your feedback for visibility about this. I've cc'd myself on the ticket and will be sure to update all of you when I hear more. Thanks.
-
Hi Tanawat,
The fact that the attributes located in the columns are moved to rows in the CSV and Excel exports is expected behaviour. From what I know there are no plans to change it in the nearest future.
-
Hi Bart I do know this is something that's being looked into. Hopefully, we'll have more news soon. Thanks!
-
Thanks for looking into this. I think the issue is in explore you set all of your "columns" as rows - and then it exports everything into a row. But if I need to see tags per week and set the ticket solved per week as a row, because that's how it splits it into columns on the dashboards, then it should also export them into columns. -- Or make it so the columns part of explore actually is a column and splits the by week section per column.
One other metric I noticed missing from insights is week solve / year. I know you have time filters - but my boss would like to see every week since 2017 by tag. A large query for sure, but as part of investor meetings - they don't showcase explore dashboards - they do so through other software products to build these based on the numbers. Insights simply had week 15 / year 2018 etc.
Thanks again for looking into this.
-
Hi Bart. From Eugene's answer above, I do know the engineering team will be doing work during the year and this feedback will be invaluable to them. I can't speak to specific timeframes, but we'll be sure to provide an update when this happens.
-
Looking for updates on this as well. This is such a basic feature Explore should not have been even released to beta without it.
-
Hi Eugene,
Are you able to give us a timeline on when we can expect the issue to be resolved now that the team are working on it?
Best,
Amie
-
+1 for a quick resolution to this issue, particularly before Insights is retired.
Thanks for the help!
Please sign in to leave a comment.
37 Comments