Explore recipe: Reporting on nested drop-down fields

Return to top

10 Comments

  • John Burns

    Hi there, my brain my just be foggy but what if we have 4 "levels"? What would category 3 prep look like? I cant seem to sort out in the attribute why its pulling level 2 vs level 3 etc. Thanks.

    John

    0
  • Tom Montgomery

    Great tutorial @..., thank you so much.

    I would like to ask the same question as @..., what would the attributes look like for a 4th level? I've tried and I just can't work the same magic!

    Your help would be greatly appreciated.

    0
  • Rob Stack
    Zendesk Documentation Team

    Hi John Burns and Tom Montgomery, I had to do a little research to get the answer to this so apologies for the delay. Here's what I received back. I hope this helps!

    LEVEL 3 PREP:
    IF (CONTAINS([Level 2 Prep],"::")) THEN
    SUBSTR([Level 2 Prep],
    FIND([Level 2 Prep],"::",0)+2,
    LENGTH([Level 2 Prep]))
    ELSE "" ENDIF 

    LEVEL 3:
    IF (CONTAINS([Level 3 Prep],"::")) THEN
    LEFTPART([Level 3 Prep], FIND([Level 3 Prep],"::",0) )
    ELSE [Level 3 Prep] ENDIF

    LEVEL 4:
    IF (CONTAINS([Level 3 Prep],"::")) THEN
    SUBSTR([Level 3 Prep],FIND([Level 3 Prep],"::",0)+2,LENGTH([Level 3 Prep]))
    ELSE "" ENDIF

    0
  • Theodore Wolf

    Hey Team,

    @...

    Is there anyways we could report on just the level 3? Or would you recommend just hiding those lower levels in the chart configuration?

    And could I potentially layer this with: https://support.zendesk.com/hc/en-us/articles/360052540974-Explore-recipe-Excluding-tickets-closed-by-merge 

    Thanks!

     

    0
  • Tom Montgomery

    @...

    If I understand what you need correctly, it's actually pretty simple. Once you have setup all the levels above, just add "[name of level 3]" to the column or row and it will only show values that come under that category.

    I hope that helps!

    0
  • Theodore Wolf

    Thanks @...!

    Essentially we want to just show the level 3, as its the "meat and potatoes" of our reporting. 

    Im curious if you'd know, could we modify the initial metric to just show solved tickets and exclude the "closed_by_merge" tag?

    We want to use this as a way to track agents solved tickets, and I think a hybrid of this post and this one would do a great job. 

    Thanks!

    0
  • Tom Montgomery

    Hey Theodore,

    We do exactly that - we exclude the tag. It works like a charm.

    I set this up almost a year ago and it took under an hour from what I remember. It's definitely worth doing.

    To exclude the tag, open up your query and under "filters" add ticket tags then type closed_by_merge in the search bar. Make sure "Excluded" is selected.

    Then, you can add "Level 3" in the Columns section and it will look something like this:

    Note: in this example I also filtered by brand to reduce the sample size.

    I hope that helps!

    1
  • Theodore Wolf

    Thanks @...!

     

    I've tried using this setup in the past, but after spot checking a few tickets, it would still include some that had the tag. Did you do any custom metrics on this query?

    0
  • Tom Montgomery

    No problem @...,

    I have noticed that too. We ignore that issue as the data gives us a good overview - a few additional merge tickets is not a huge problem to us. The solution in the article you shared above might be your best bet.

    Maybe one of the Zendesk team can give some more insight into why the exclude tag feature is not 100% reliable.

    0
  • Rob Stack
    Zendesk Documentation Team

    Hi Tom Montgomery, I wasn't completely sure so I've opened a ticket so someone on the team can investigate. Hopefully, you'll here from someone soon.

    0

Please sign in to leave a comment.

Powered by Zendesk