在许多基于时间的报告,探索使用24-hour clock format and you can't change this. Using a simple report, this recipe shows you a way you can change how times (and other things) are displayed usingrenamed sets.
This article contains the following sections:
What you'll need
技术水平:Medium
Time required:20 minutes
- Zendesk Explore Professional or Enterprise
- Editor or Admin permissions (seeGiving agents access to Explore)
- Ticket data in Zendesk Support
- Some experience creating reports with Explore
How to create the initial report
这份报告显示了ti的数量ckets created at each hour of the day. If you need more help to create the report, seeCreating reports.
- In Explore, create a new report using theSupport: Ticketsdataset.
- Add the metricTicketsto theMetricspanel
- Add the attributeTicket created - Hourto theColumnspanel.
Explore generates a chart that looks similar to this:
Notice how the time on the X axis is listed in 24-hour format. In the next procedure, you'll learn how to change this so that the time reads as 12-hour format. For example,15will read as3pm.
How to use a renamed set to change the time format
In this procedure, you'll create a custom attribute that renames the times from theTicket Created - Hourattribute to be in a 12-hour.
- With the report you created open, open the calculations menu ().
- UnderAttributes, clickRenamed set.
- On theRename valuespage, enter a name for your custom attribute, for exampleTicket created - 12 Hour.
- From theComputed fromdrop-down list, choose the attribute you want to rename values for, in this caseTicket created - Hour.
- You'll now see a list of all stored values for the attribute. In the text box next to each value, type the value you want to display in the chart instead of the current value.
Tip:In your list, you might notice that some hour values are missing. This is because your report did not pick any results up for that hour, therefore it has no value. If data is generated later for the missing hour, you can come back and edit this attribute.
- When you are finished, clickSave. You now have a custom attribute containing a renamed set. Add the custom attribute to theColumnspanel in place of theTicket created - Hourattribute.
This gets you half way. However, Explore now treats the renamed values as text strings, and sorts them as such. If you try to use this attribute, you'll see something like this:
To fix this, you'll need to create another new attribute that contains an ordered set generated from your renamed set.
To create the ordered set
- With the report you created open, open the calculations menu ().
- UnderAttributes, clickOrdered set.
- On theCustom orderpage, enter a name for the new attribute. This will be the attribute you use to create the final report, so give it a descriptive name likeTickets Created - 12 Hour Ordered.
- From theComputed fromdrop-down list, select the attribute containing the renamed set you created previously,Tickets Created - 12 Hour.
- You'll see a list of the possible values for the attribute. Drag and drop these into the correct time order.
- When you are finished, clickSave.
Now, you can replace the column attribute you previously used with your new attribute,Tickets Created - 12 Hour Orderedand your chart will now display correctly with the correct time legend.
Next steps
You can find more information about renamed sets inOrganizing values by groups and sets.
1 Comments
HeyRob Stack
Thanks a lot for the article, I used the Ordered Set on a report on Full Resolution Times but created some custom brackets before.
I might be doing something wrong though, the report works with the new brackets, when I create the new Order Set and select the old report I also get the correct brackets which I can then re-arrange:
However, when I then replace the column attribute with the new Ordered version, I receive the following error:
Edit: For some reason trying this the day after, it suddenly worked.
We have been experiencing these kind of things a lot with the beta dashboard, where things aren't working in the moment, but then suddenly do at a later time.
Is this a known issue currently when working with the beta dashboard?
Pleasesign into leave a comment.