On July 8, 2019 we plan to release a fix that will update all of your pre-built datasets to the latest version and ensure that the metrics and attributes in each dataset are synced to the latest version whenever we add something new.
How does this impact you?
With this update, there are potentially a number of changes that you will see to your pre-built datasets in Zendesk Explore:
- We have renamed your prebuilt datasets and added the suffix [Default]
- You will no longer have the ability to edit default metrics and attributes
- You may see that some metric and attributes have new names and belong to new folders
- All your custom metrics and attributes will now be located in a ‘Calculated Metrics’ or ‘Calculated Attributes’ folder
- The data structure menu will be removed and the ability to update data aggregators and change display formats will be moved to the edit metric dropdown
Note: Published dashboards will not be impacted until dashboards are republished with new changes.
What are the benefits for you starting July 8th, 2019?
- You may have access to a number of new metrics and attributes
- All of your datasets will seamlessly be updated to the most recent version
- When cloning dashboards, pre-built datasets will no longer be cloned
Does this impact my custom datasets?
Any custom datasets that you created before July 8th, 2019 will remain unchanged.
What action do I need to take?
This is a great opportunity to clean up the datasets that your team is no longer using. Between now and July 8th, 2019, we suggest you take the following actions:
- Understand how to update your calculations and queries, see Getting started creating queries
- Learn how to clone queries and calculations to another dataset, see Working with Datasets
- Review the metric and attribute reference articles to understand the latest metric and attribute names that will be available in the default, pre-built datasets. See Metric and Attribute Reference for more details
- Remove datasets that your team is no longer using
22 Comments
Hi Vincent! To clarify - will this mean that any existing custom datasets will become out of date and will not be updated to the most recent version?
Hi Chris, that is correct. We have decided not to update your custom datasets to minimize short-term impact. You will be able to copy any query to a managed dataset and adopt the new model at your own pace. On that note, we are also planning add'l improvements in Q3 to make sure we make it much easier for you to identify which dataset to use.
Hi Vincent, looking forward to this update!
I'm wondering if this is related because I have not seen an announcement on this:
I've just noticed last week, that now some of my custom fields (at least the drop down) are showing their actual values in queries whereas before it would just show the tag assigned to that value (although it's still showing tags for old values that have been deleted long ago).
Hi Quentin, thanks for reaching out.
We have indeed deployed last week a long awaited improvement to ensure you can report on user-friendly custom field values, instead of their technical tags (see product feedback: https://support.zendesk.com/hc/en-us/community/posts/360029584473-Display-Label-for-a-field-instead-of-tag-value-).
And here's the announcement for last week's change: https://support.zendesk.com/hc/en-us/articles/360022689213
Hope that clarifies!
@Vincent
About 6 months ago i had created some custom datsets and they got corrupted after a period of use.
With conversation back and forth with Zen support they basically said i will have to use the new last updated Zendesk standard ones. And make new custom ones from them.
I ended up having to recreate all my reports from scratch which was no fun. and more importantly wasted a lot of company time.
So 2 questions
1) Is there a way to change a query to another dataset. of the same type? so if this happened again i can just adapt the query to use the standard dataset?
Like clicking that and we can select the standard one? Or some other way of doing it?
2) What do i do if yours becomes corrupted ?
We are worried that it will happen again and im sure my bosses will go nuts if i have to recreate our company reports from scratch again.
Thoughts?
Small edit
Are these the ones you mention are the standard ones?
If so why dont the chat and talk have the same ending?
Hey Jeremy, thanks for reaching out. I assume hat "corrupted" was referring to metrics or attributes that were no longer supported. The intention of this major change is to ensure that you're always on the latest version - so this situation should no longer happen. As mentioned, this change will only impact your default/prebuilt datasets - however from there on, all custom datasets will also become "fully managed".
In parallel to this release, we're also working on a bunch of improvements that will make it easier for you to manage your environment. All of these should help you reduce the number of datasets in use (incl moving queries between datasets), and the time it takes to figure out which dataset to use. I should have more information shortly re. timeline.
The "Default" datasets a.k.a "prebuilt" datasets will all be renamed with the "Default" suffix on the day of the deployment (July 8th). That will include Chat and Talk.
There was never a firm reason, Zendesk coulndt give me an answer why. so i dont really know what caused it
Not bothered about the timeline so much as having to recreate all my stuff again..
I wish there was a simple way to backup these things so i can recover..
But if the underlying data changes then you are bound to expect problems i guess.
So roughly you are making the defaults more bullet proof then?
I have no idea what you mean about moving queries from one to another..
And what does fully managed mean?
Assuming you can say at this point. :)
Regarding:
Just to clarify.. I should be moving all my queries OFF the datasets ending [Default] currently? I'm in the process of doing that after Zendesk support alerting me to this when I had a query, so just want to check I'm not going in the wrong direction. Thanks!
Fiona
Hi Fiona,
I can confirm, if you are moving to custom datasets you can keep that up. The custom datasets will have the most up-to-date schemas at this time. I recommend renaming the custom datasets with the date they were created in case any future changes occur.
Hope that helps!
Hi Vincent,
Just to check, will this impact Insights reporting?
Thanks!
Hi Paula - This update will only be reflected in Explore, not Insights.
Thanks Andrew!
Hi Zendesk folks,
One of the changes described is: "You may see that some metric and attributes have new names".
What does this mean for:
Thanks,
Hi Jeremy,
We've introduced an underlying new architecture which will give us the ability to update all "managed schemas" at once, starting July 8. A "managed dataset" means that whenever we add a new metric or attribute (or just fix a definition, add a folder, clarify a particular name etc.) for an existing dataset, we'll be able to push that change to all "managed datasets". This means that your "managed datasets" will always be on the latest version. No need to create new datasets to get latest updates. Yay!
By "moving queries" between datasets, I meant that we're looking at adding the possibility for you to move a query between one of your existing "unmanaged" custom dataset over to a "managed" dataset - without having to update your dashboards. That should give you much greater flexibility in organising your datasets and queries without impacting your dashboards. I don't yet have a firm timeline - we'll let you know when we have more visibility.
Hi Paula,
Clarification - the dataset renaming (adding [default] extension) will take place on July 8th. On that day, we'll update & rename your prebuilt/default datasets. We will not touch your custom datasets to minimize impact. However all custom datasets created after July 8th will be managed.
If you're in the process of re-organising your queries, you may want to move them over to your prebuilt/default datasets. As we will not be updating custom datasets on July 8th, I would not recommend moving your queries to custom datasets created before July 8.
Hi Gal,
Renaming of metrics/attributes will not impact calculated metrics/attributes or filters that you may have created.
Hope that clarifies!
@Vincent
So for the custom ones i have at the min.
A) Do they stay as they are and i need to remake them from the new ones after the change? To keep them updated for the future.
B) Do they get updated once the change is sorted and i keep using them?
Hi Jeremy - the answer is A). Your existing custom datasets will not be updated to minimize impact on your current reports. The recommendation is for you to - eventually - move your existing queries over to new datasets. As I mentioned, we're planning to make it easy for you to move your queries between your unmanaged datasets and new managed datasets. More information on timeline will follow.
Ok thanks
just trying to be clear
Hi,
Regarding the possibility to move queries over new dataset, do you any update ?
Hi Chloe, thanks for reaching out. Good news - we are working on this! We're in the process of interviewing some customers to ensure the designs will address key needs. Would you be interested in having a look at our prototypes and share your feedback? Thanks
Hi Vincent,
Yes sure, I'm interested ! I have more than 250 queries and 11 dashboards. I really need this feature.
Yeah i have over a hundred the same.
Going to be a long old job to get them all on the new ones
Atm im cloning the old one then going to the report and adding the clone and delete the old one, then reshape till it fits where the old one did and repeat....
Please sign in to leave a comment.