Following recent schema updates (see announcement) to Zendesk Explore, we are excited to introduce additional improvements that will help Explore admins and editors to better understand what datasets to use when creating queries.
Updates to the Dataset Library
There are two primary updates we've made to the datasets library and related Explore features.
First, we now show a dataset status icon to help you better understand the differences between your datasets in Explore. You’ll now notice the following icons in the dataset:
- Default means that this is the dataset Zendesk has created for you, accessible by all of your editors.
- Out of date means the dataset was created before July 8th 2019 and won’t receive any further updates.
Second, we understand that the current Last refreshed indicator has been causing confusion for a number of users. We will be moving this information to the Query Builder over the coming months. In the meantime, we've replaced Last refreshed with the Creation date.
Dataset Selection Improvements
We’ve introduced a guided approach to selecting which dataset that users create a query from. This enhancement aims to make it easier to select the right dataset to analyze.
Here’s what the new workflow looks like:
- Select a data source, such as your Support or Chat channel.
- Select which dataset type you want to use.
- Select the dataset on which you want to build your query.
Each data source has a variety of datasets available. As you select a dataset type, you’ll also notice that their definition is highlighted, so you can better understand the contents and what each dataset type enables you to analyze.
Finally, each dataset belonging to a given type now shows more details like status and the number of queries associated with it, so that you can select the right one more easily.
We want to hear your feedback
If you have any feedback on our new releases, we’d love to hear from you. Add a comment below, share it in our Community forum.
For more information, see Working with datasets.
9 Comments
So is there a way to migrate a query from an out-of-date dataset to a current dataset? Or can we update the datasets manually?
Hi,
i want to know the same thanks!
/Tobias
I like the improvements however, what do you mean by "won’t receive any further updates."? Does that mean that for those queries the number of tickets will not show after july9th? or that new ticket fields won't show up?
Anyway, does that mean I will have to clone all my queries to a non-outdate data and replace all queries on my dashboards?
Thanks.
Dear all, we're planning to introduce the ability to move queries between datasets so that you don't need to recreate queries manually. We'll share more information on the timeline shortly.
"Out of date" datasets mean that these datasets are using older versions of metrics & attributes, and that we will not be able to update them with newer metrics & attributes. However, the data available through these datasets (like number of tickets) will keep on being updated, and new ticket fields will keep on showing up.
Hi Vincent and Andrew,
For the "Last Refresh", you say this has been moved to Query Builder, can you indicate where this is please.
thank you, Mark
Hi Mark, the "Last refresh" indicator in the Query Builder should reach production in the coming weeks. It will be displayed under the "dataset name", and updated whenever data is rendered (table, chart etc.) so that you can understand what data you're seeing
Hi Mark Hinson, following up on that earlier discussion - we've published the changes that now display the "Last Refresh" information within the Query Builder (under the dataset name).
Hi Team,
I would like to thank you about the new update coming this week (or maybe last week, not sure)
But...
We currently have some problem to create the report because the dataset has been change. Now the data only shown for an hour ago while we need the data from a month ago. So can you please help us to change this like before?
Thank you
Hi Makmur Arafat, thank you for reaching out. This "Last updated" indicator shows when we last got data for that specific dataset, so that you can better understand the tickets / updates you are looking at. However you can still access data that was created/updated months ago. This update should therefore not impact any of your existing reports. If you have any issues, feel free to submit a ticket and we can help you investigate possible issues with the query. Kind regards
Please sign in to leave a comment.