Zendesk Explore - Month Year Custom Attribute Incorrect Order

Beantwortet

3 Kommentare

  • Gab Guinto
    Zendesk Customer Care
    Hi Robin,
     
    It is the expected behavior for attributes like this – those combining multiple date attributes – to be ordered alphabetically by default, even when the option 'Sort like time attribute' is ticked. 
    • Sort like time attribute: If your calculated attribute represents dates, this option places your date values in the correct order.
      • Note: This option applies only to single attributes. Combining attributes, such as adding a year to the end of a month, will result in sorting alphabetically instead of chronologically.
    I'm afraid there's no option to customize the attribute formula to have the values listed in chronological order. 
     
    A workaround that I can recommend, if you're working on a Table-type query, is to add the default Year and Month attributes before the custom attribute date and then just hide those columns (via Chart options menu). This way, the column for your custom Month-Year attribute will display the values chronologically. But, for other chart visualization types, this workaround would not be applicable; using Ordered sets might be the best option for other query types. 
    1
  • Hi Gab,

    I'll try to incorporate that in the tables, and I guess the graph reports will need to use the single attributes month and year for now.

    Is this something that is ever to change or is being worked on? Surely it can't be considered correct to have these sort alphabetically when they a formats of date attributes?

    1
  • Gab Guinto
    Zendesk Customer Care
    Hi Robin,
     
    We could not tell for sure yet if this is in the roadmap. But I definitely agree, it would make more sense if the values are sorted chronologically. Hope this will be addressed soon. If you have some time, I recommend that you start a post about this in our Product Feedback topic. Our Product team actively monitor our feedback threads, and conversations with high user engagement ultimately gets flagged for planning. 
    1

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Powered by Zendesk