Filter numeric fields in Explore

Terminée

5 Commentaires

  • Andrew Forbes

    Hi Fabio - This is possible today by adding a "Metric filter" to your dashboards. See below: 

     

    0
  • Fabio Strasser

    Hi Andrew, 

    thanks for your answer! I tried that of course, but didn't think it would be necessary to have that metric included in my query. So it works now but not the way I want to...

    I didn't want the numeric value visible as a metric, because as mentioned above it contains Codes. So I don't want to show the AVG or SUM or whatever else of this metric. I just want to filter the code range as mentioned above.

    So if I display Tickets by month and I only can have to SUM or AVG of my Codes as metric, the displayed value will just be useless.

    0
  • Peter Godden

    I would also like to be able to slice my reports based on a value entered into a numeric field or text field. The use case is that you may have several tickets all relating to the same project. Being able to measure things based on a  "project ID" or a "project name" would allow for tracking time across whole projects rather than specific tickets. Back in Insights, it would automatically convert text fields into an attribute that you could then slice a report simply by checking a box under "HOW". In BIME, you can actually decide if a text or numeric field is considered an attribute or metric. Why can you not make this specification in Explore? Can you please make improvements to Explore to allow for slicing reports based on numeric or text field data? 

    0
  • Eugene Orman
    Zendesk Product Manager

    Peter Godden, This article explains how Support custom fields are mapped in Explore - Reporting with custom fields. In short, numeric custom fields appear as the metrics and text custom fields appear as attributes by default. 

    So, ideally before creating a custom field in Support, the admin needs to think through how this field will be used for the reporting. If the field values are numbers but they refer to the IDs or codes that don't need to be counted the best field type is Text or Regex. 

    However, if you want to convert a metric into an attribute or other way around you can do it via a calculation in Explore. 

    To convert a metric into an attribute create a Calculated attribute with this formula:

    VALUE(Numeric field name)

     

    To convert an attribute into a metric create a Calculated metric with this formula:

    NUMBER([Text field name])

     

    To cover the use case that Fabio Strasser mentioned you can do the following:

    IF NUMBER([Text field name])>500 THEN "> 500"
    ELIF NUMBER([Text field name])<=500 AND NUMBER([Text field name])>300 THEN "300-500"
    ELSE "0-300"
    ENDIF

     

    1
  • Rob Stack
    Zendesk Documentation Team

    Hi all, we've just published a new recipe that goes into a bit more detail about this - https://support.zendesk.com/hc/en-us/articles/360049655173

    0

Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk