Recherches récentes
Pas de recherche récente

Chris Gould
Adhésion le 16 oct. 2021
·
Dernière activité le 14 déc. 2021
Suivis
0
Abonnés
0
Activité totale
21
Votes
7
Abonnements
6
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Chris Gould
Chris Gould a ajouté un commentaire,
+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.
Afficher le commentaire · Publication le 14 déc. 2021 · Chris Gould
0
Abonnés
2
Votes
0
Commentaire
Chris Gould a ajouté un commentaire,
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
Afficher le commentaire · Publication le 29 sept. 2021 · Chris Gould
0
Abonnés
0
Votes
0
Commentaire
Chris Gould a créé une publication,
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"))
Publication le 28 sept. 2021 · Chris Gould
1
Abonné
2
Votes
3
Commentaires
Chris Gould a ajouté un commentaire,
Hi @... - just wondering if there has been any changes in regards to reporting on SMS messaging in explore?
Afficher le commentaire · Publication le 20 sept. 2021 · Chris Gould
0
Abonnés
0
Votes
0
Commentaire
Chris Gould a ajouté un commentaire,
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”)
Afficher le commentaire · Publication le 13 août 2021 · Chris Gould
0
Abonnés
0
Votes
0
Commentaire
Chris Gould a ajouté un commentaire,
@...,
I have been told by my ZD account manager that it's likely a Q4 (US FY) release.
Afficher le commentaire · Publication le 08 juil. 2021 · Chris Gould
0
Abonnés
0
Votes
0
Commentaire
Chris Gould a ajouté un commentaire,
How is this not a feature? I hope it has changed since this was posted.
Afficher le commentaire · Publication le 24 juin 2021 · Chris Gould
0
Abonnés
1
vote
0
Commentaire
Chris Gould a ajouté un commentaire,
Hi - is this still on track for delivery in H2 2021?
Afficher le commentaire · Publication le 17 juin 2021 · Chris Gould
0
Abonnés
0
Votes
0
Commentaire