• Chandra Robrock

  • 10 de diciembre de 2020 03:39

  Community Moderator

  Hi Maxime Joannette - It looks like you're receiving this error because you're trying to subtract a date attribute field from another date attribute field. Instead, I wonder if this will get you closer to the end result you're looking for.

  First, try selecting Tickets and Solved Tickets under the Metrics section.

  Next, select the specific date field you'd like to filter this data by (ex: Tickets updated - week of year) under the Column or Rows section (depending on what type of graph you're ultimately looking to build).

  From there, click on Result Manipulation > Result Metric Calculation. This is where you could then build your COUNT(Solved tickets)-COUNT(Tickets) metric.

  I haven't built this exact query before (aside from quickly testing it in my own instance) so another community member might have a better & more specific recommendation based on what's worked well for their team, but I hope that helps point you in the right direction.

• Maxime Joannette

  • 10 de diciembre de 2020 14:35
  • Editado

  Thanks for the suggestion Chandra M, I tried but here's my conundrum:

  I'm only looking to get a singular number : This week's input/output differential

  The thing is, filtering will not yield the expected results.

  I can either pick "Time - Ticket Created - Week of year" or "Time - Ticket Solved - Week of year", which restricts both metrics, yet I need to have each filter be applied to their respective metric (so far so good on that, used Calculated Date Range metric to achieve this), otherwise I'm missing tickets that were opened last week and solved this one, or opened tickets that aren't solved yet.

  So I have the two calculated metrics side-by-side on a simple table:

  
  
  But I can't figure out how to get a third column there that simply does 1 - 2. I don't mind using a new query to compute this single difference, but so far have been unsuccessful.

• Chandra Robrock

  • 11 de diciembre de 2020 14:07

  Community Moderator

  Maxime Joannette Out of curiosity, did you try using the Result Manipulation > Result Metric Calculation route?

  I'm not 100% sure if that would work with the calculated metrics you created but it did seem to work well when I played around with it the other day using the standard Tickets & Solved Tickets metrics. 

  Here's what the result metric calculation looks like on my end:

  

  Once I click on the Add button, Explore adds this new metric as a third column to the table:

   

  

  Mind checking to see if that option works for the calculated metrics you created? If so, do you think that could work for your use case?

• Maxime Joannette

  • 11 de diciembre de 2020 14:23

  Yes, sorry I should have mentioned I tried this too, I only get an "equal" there:

  

  Thanks anyway!

• Chandra Robrock

  • 14 de diciembre de 2020 14:36

  Community Moderator

  Maxime Joannette If you wouldn't mind sharing the exact Calculated Date Range metrics that you built, I'd be more than happy to continue digging into this to see if I can help. 

• Maxime Joannette

  • 14 de diciembre de 2020 16:35

  I wish I kept what I did last time, but ended up deleting it since it didn't meet my requirement.

  I tried it again and it looks like it now works!

  

  Result Metric Calculation:

  

   

  Thanks for all your help Chandra M!

• Chandra Robrock

  • 15 de diciembre de 2020 14:42

  Community Moderator

  Maxime Joannette Awesome, happy to hear that worked for you (plus, I learned a new Explore trick myself). :)

  Enjoy the rest of your week!

Iniciar sesión para dejar un comentario.