Búsquedas recientes
No hay búsquedas recientes

Chris Gould
Incorporación 16 oct 2021
·
Última actividad 14 dic 2021
Seguimientos
0
Seguidores
0
Actividad total
21
Votos
7
Suscripciones
6
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Chris Gould
Chris Gould hizo un comentario,
+1 - I've just spent ages trying to understand why the field isn't visible to me. "Is this an explore issue or an agent issue"? Would be good to see it, regardless of whether data exists or not.
Ver comentario · Publicado 14 dic 2021 · Chris Gould
0
Seguidores
2
Votos
0
Comentarios
Chris Gould hizo un comentario,
Hi @...S O'Callaghan,Yes the formula definitely works, however, I need to function as a date. Not just a normal attribute field.
So I would like to apply ranges to it like you might with ticket created-date and ticket solved - date.
For example: show me the "New attribute" for This month
Ver comentario · Publicado 29 sept 2021 · Chris Gould
0
Seguidores
0
Votos
0
Comentarios
Chris Gould creó una publicación,
Hi everyone,
I'm hoping this is a obvious/simple solution.
I am trying to do some rough forecasting which looks at a date 90 days after the ticket is solved. I'd like the attribute to behave like a date attribute where I can apply ranges or ideally even split into weeks and months, however, I know the latter requires extra work.
Here is my code so far and I'm stumped as to why it's not appearing as a date.
DATE(DATE_FORMAT(DATE_ADD([Ticket solved - Date], "day", 90), "yyyy-MM-dd"))
Publicado 28 sept 2021 · Chris Gould
1
Seguidor
2
Votos
3
Comentarios
Chris Gould hizo un comentario,
Hi @... - just wondering if there has been any changes in regards to reporting on SMS messaging in explore?
Ver comentario · Publicado 20 sept 2021 · Chris Gould
0
Seguidores
0
Votos
0
Comentarios
Chris Gould hizo un comentario,
We just used DATE_FIRST_FIX function to find the time the first call was made against a ticket ID, given a ticket can have multiple calls, DATE_FIRST_FIX was ideal.
We were able to nest this into a DATE_DIFF to find the length in time between the ticket creation and the first call. You can then aggregate any way you like as there is only one value provided per ticket ID.
DATE_DIFF(DATE_FIRST_FIX([Call - Timestamp], [Ticket ID]), [Ticket created - Timestamp], “nb_of_minutes”)
Ver comentario · Publicado 13 ago 2021 · Chris Gould
0
Seguidores
0
Votos
0
Comentarios
Chris Gould hizo un comentario,
@...,
I have been told by my ZD account manager that it's likely a Q4 (US FY) release.
Ver comentario · Publicado 08 jul 2021 · Chris Gould
0
Seguidores
0
Votos
0
Comentarios
Chris Gould hizo un comentario,
How is this not a feature? I hope it has changed since this was posted.
Ver comentario · Publicado 24 jun 2021 · Chris Gould
0
Seguidores
1
Voto
0
Comentarios
Chris Gould hizo un comentario,
Hi - is this still on track for delivery in H2 2021?
Ver comentario · Publicado 17 jun 2021 · Chris Gould
0
Seguidores
0
Votos
0
Comentarios